(-c (Optional) Returns the current state of the job and the names of any jobs that depend on it.)
OUTPUT: =======
Job Name Status/Exec. Mode Date Cond? Start Cond? Dep. Cond? -------- ----------------- ------------ ----------- ---------- test-Oct27 SUCCESS No Yes No
Condition: s(JobABC) Atomic Condition Current Status T/F ---------------- -------------- --- s(JobABC) *NOT_EXIST* F
--------------------------- Another way to check job dependencies: jil -V batch < inputfile:
-V none|job|batch|syntax Specifies whether the JIL processor should verify the validity of the job definitions and that jobs specified in the job dependency conditions actually exist in the CA Workload Automation AE database.
The jil -V Batch would be used when loading jobs into the Database, if they exist, it tries to INSERT them again. Below is an example of loading a jil file with 1 job definition, with a non-existing condition job. Whether the job(s) exist or not the report will still identify missing conditions.
CAUAJM_I_50323 Inserting/Updating job: test-cond CAUAJM_W_10282 WARNING for Job: test-cond. The date_conditions attribute is FALSE. The scheduler will ignore date attributes CAUAJM_I_50205 Database Change WAS Successful!
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 ------------------------------ --------------------------------------------- ---------------- test-Oct27 JobABC Job test-cond JobABC Job ______________________________________________________________________________