Condition job in cross instance
search cancel

Condition job in cross instance


Article ID: 38550


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent


In the same instance, when the condition job not exist then jil is giving warning message. 

But if I refer the condition job from a different instance, jil is not giving any warning message when job is not exist. 

The warning message in the following :


CAUAJM_W_50258 *** WARNING: The following Jobs have starting conditions that depend on nonexistent Jobs or Global Variables: 

Job Name Missing Condition Job Name or Global Variable Condition Type.


Why is the behavior different in these situations ?




Release: ATSYHA99000-11.3.6-Workload Automation AE-High Availability Option


That is how it is designed. 

 In the same instance, all artifacts (jobs/Global variables..etc) are in the same Database and so they are used to cross check and throw a warning when they are not defined. 

 The way cross instance works is different. 

 1. Cross instance has to be defined <If the external instance is not defined, JIL throws an error and comes out>

 2. then when a job is defined with an external dependency, an event is sent to other AutoSys Server for the status of the dependent job. 

Until this point, there is no communication between the two instances.