CA7

CA7 is an enterprise-class job scheduler that runs primarily on IBM z/OS mainframe systems. It automates the scheduling, monitoring, and management of batch jobs and workflows.

Throughout this documentation, the term "task" refers to a scheduled task defined in the scheduler, to avoid confusion with JCL jobs.

JOB NAME

The value of JOB NAME column is the scheduled task name, where it could be different from the actual invoked JCL name. To make it unique throughout the dependency analysis, the scheduled task name is a combination of JOB NAME, line number of current job - 1 and the scheduler file name.           
For example, assuming the CA7 scheduler file name is: myScheduler.ca7 and part of the content is shown below, then the first scheduled task name is: OPENFIL-0-myScheduler.ca7.

1LJOB,JOB=OPENFIL,LIST=ALL
JOB=OPENFIL LIST=ALL                                  DATE=06.198    PAGE 0001
  JOB    ----JCL----   SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN
  NAME    ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME
OPENFIL 255 OPENFIL CARDDEMO  000 ALL  *NONE* 000652 005 000 1058  06198/0700

JCL MEMBER

The value of JCL MEMBER column implies a link from the scheduled task, see JOB NAME, to the corresponding JCL file; in the example below it is the CLOSEFIL.

   JOB    ----JCL----   SYSTEM  USR MAIN PROSE  SCHED  --NUMBER OF-   LAST-RUN
   NAME    ID  MEMBER   -NAME-  -ID -ID- DSNBR  DSNBR  STP DDS RUNS   DATE/TIME
 JOBNAME 255 CLOSEFIL CARDDEMO  000 ALL  *NONE* 000652 005 000 1058  06198/0700

Unconditional link

TRIGGERED JOBS and TRIGGERED BY

TRIGGERED JOBS and TRIGGERED BY express the same dependency between two tasks, but from opposite sides:

• TRIGGERED JOBS is declared on the parent task and lists the tasks it triggers.
• TRIGGERED BY is declared on the child task and names the task that triggers it.

Both produce the same dependency edge: an "Exec Next Scheduled Task" link from the parent to the child.

JOB

The value of JOB can imply the next scheduled task name.

SCHID

The value of SCHID can imply the next scheduled task schedule ID.

TRIGGERED JOBS example

 1LJOB,JOB=CLOSEFIL,LIST=ALL
 .
 .
 .
--------------------------- TRIGGERED JOBS ----------------------------
  JOB=ACCTFILE SCHID=030      QTM=0100 LEADTM=0000 SUBMTM=

This block can exist in a Job list line, but is not mandatory. When the block exists, it builds a link between the listed job and the triggered job.      
In the example above, Job CLOSEFIL will trigger job ACCTFILE.

TRIGGERED BY example

 TRIGGERED BY: JOB=PARENTJOB SCHID=030

In the example above, the current task is triggered by PARENTJOB with SCHID 030; 
When the parent task exists in the file and its SCHID matches, the dependency is resolved as a normal "Exec Next Scheduled Task" edge from the parent to the current task. 
When the parent task is absent from the file or its SCHID does not match any of the parent's SCHEDULES, a missing "Exec Prev Scheduled Task" edge is created.

TRIGGERED BY with TYPE=DSN

TRIGGERED BY also supports TYPE=DSN, where the trigger is a dataset rather than a task. This is the only difference with TRIGGERED JOBS, which does not support dataset triggers. In this case, the current task becomes an entry point with the SCHID from the dataset trigger.