Job stays in Event Wait status using the dependency condition with "If planned" option

Products

• CA Automic Dollar Universe

Issue/Introduction

The dependency condition of the uproc with "If planned" mode does not work as expected.

For example, the uproc WAIT305 has parallel/OR dependency on uproc WAT110(C01) parallel/OR WAIT105(C02) and the uproc WAIT105(C02) is not scheduled in this scenario. The parallel/OR condition means that if either of the condition is satisfied, the uproc WAIT305 can execute. 

The dependency on the uproc WAIT105 is set with "If Planned".

 

When the uproc  WAIT305 is executed, the execution will stay in "Event wait".

The history trace shows that it is waiting for the event of the uproc WAIT110 but the uproc WAIT305 should have executed since it may have satisified the depedency on the uproc WAIT105. 

---------------------------------------------------------------------------------------------------------

20230320101355  Start Condition Check
                   Modified directly in the Engine by
                   operator : administrator
                   Processing Date 20230320
20230320101355  Cond: 002 Skipped | Uproc: WAIT105 | MU: MANAGEMENTUNIT | User: administrator | Processing Date: 20230320

Dependency    Cond. 001 Prop. 01 :
Depe. :  -  WAIT110 -  MANAGEMENTUNIT 20230320  Missing
 *** Task launch refused  ***

---------------------------------------------------------------------------------------------------------

Environment

Component: CA Automic Dollar Universe

Release : 7.x

Cause

By design

Resolution

According to the documentation below, the execution of the WAIT305 should stay in "Event wait" until the condition of the uproc WAIT110 is satisfied.

--------------------------------------------------------------------------
The "If planned" option allows subtracting the condition of the launch formula if the expected job is not present in the job event database and is not scheduled (checked in this order). This avoids unnecessary waiting or complex workarounds if the conditioning job is not scheduled at the same frequency as the conditioned job. This can simplify the production start of a periodic session by avoiding creating the first event manually during initialization.

The principle is as follows:

-If the event is present or if the launch is scheduled, the launcher performs the analysis of the condition and the launch formula as usual.
-If the event is not present and the launch is not scheduled, the condition is completely ignored until the next possible condition check (regardless of the events that could be created or the external interventions).

--------------------------------------------------------------------------

Reference:
https://docs.automic.com/documentation/webhelp/english/ALL/components/DU_AS/latest/Dollar%20Universe%20Guides/help.htm#DUAS_ref/Precondition%20Checks.htm?Highlight=If%20planned

So basically, the condition with "If planned" will be removed from the launch formula if the expected job is not present in the job event database and is not scheduled. In the case of WAIT305 , there's parallel/OR condition with WAIT105(IF PLANNED checked)=C01 and WAIT110=C02. Since the event of WAIT105 is not present and it is not planned/scheduled, then it will be removed from the launch formula, leaving only the condition C02 to be checked. As a result, the execution of the uproc WAIT305 will stay in "Event wait".