Trigger Sequencing:  CA-7 provides a 'look-back' facility on predecessors, so a successor job can check that a predecessor has run within a specified number of hours. However, this facility can cause problems if the application is required twice within that time frame. To prevent this possible problem, the jobs are always triggered early enough to ensure that no 'look-back' is necessary . Here you can see that JOBI is requested by JOBB to ensure it will 'see' the execution of JOBG and JOBH. To be honest, working out the optimum point to trigger a job was a bit of a mathematical nightmare!

PGM80-95: These programs calculate the trigger structure. PGM90 also produces a list of any predecessors which the package feel is not required. In the diagram above you can see there is no need for JOBC to wait for JOBA because it is also waiting on JOBB which will not execute until JOBA has completed. PGM95 allocates the schedule ID number to each application. This is just an incremented number which is bluntly, not very clever. Some sites may require allocating the numbers in a different way. If this is the case you will need to edit PGM95APP yourself.

General Workstations: All general workstation jobs are renamed. The first 4 letters of the name is the workstation type, SETP MAST etc and the last 4 is an incremented number. As standard, the package defines these to CA-7 as dummy (EXEC=N) jobs. The idea behind this design is that it is easy for operations staff to identify all the general workstations jobs. Also, either text messages (USER requirements)  can be allocated to these jobs or JCL if the task is automated. SETPs are handled in a different way to ensure all overnight tasks can be seen during the previous day.