THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK 

----------------------- CA-7 CPU JOB PREDECESSORS -----------------------

FUNCTION: LIST     (FORMAT,LIST,UPD)
PRED FOR JOB: JOBB                        LIST-SCHID: 3
OPT SCHID LEADTM    PRED-JOB  NEXT-RUN

 *   000  0000      JOBA1         YES
 *   000  0012      ?JOBA2       ONLY
 *   003  0099      JOBA3        SKIP
 *   003  0000      /JOBA4       SKIP









PROGRAM SM20   MSG-INDX: 00       -- DB.3.2  --      99.365 / 23:59:59
MESSAGE: LIST SUCCESSFUL
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The FUNCTION field.

You must type in LIST FORMAT or UPD here when working online. Don't forget if you want to re-execute a function you must over-type at least one character. See below for details on the different functions.

When defining job requirements via batch terminals, the function is the first positional parameter.

THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The FORMAT Function.

This function is used to clear the screen of all input, that's all! It's always a good idea to clear the screen performing a LIST function on a new job, even if you know it hasn't got any requirements! You can't use this function when using the batch terminals.
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The LIST function.

This function is used to display all the requirements defined to one job, it can only be used online and not in a batch terminal. It can be used in conjunction with the LIST-SCHID field to list requirements of a specific SCHID. If there is more than one page of requirements, use /PAGE+1 to page forward.

THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The UPD function.

This function is used to alter the requirements of a job. It doesn't matter if you are adding, updating or deleting requirements, you always use this function. The type of change is defined in the OPT column.

THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The PRED FOR JOB field.

The dependent job. In this example JOBA1 must run before JOBB will be released. JOBB will only wait for JOBA2 if JOBA2 is on one of the queues when JOBB is requested - a conditional dependency. The dependency to JOBA4 is coded with a / This means JOBB would not be released if JOBA4 has been submitted. Note a second negative dependency the other way round must be added to ensure that JOBA4 would be held if JOBB has already be submitted. The LEADTM field value is not used in with negative dependencies.
Batch terminal syntax: 
JOBCONN
UPD,JDEP,JOBB,OPT=A,PRED=JOBA
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The LIST-SCHID: field.

Only used with the LIST function. Here all dependencies defined with a SCHID of 3 or 0 are listed. Only used online.
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The OPT field.

You can code values of "A" to add a new requirement, "U" to update an existing trigger (note the SCHID and PRED-JOB fields cannot be updated), or "D" to delete an existing trigger.

Batch terminal example: 

JOBCONN
UPD,JDEP,JOBB,PRED=JOBA1,OPT=A
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB TRIGGER SCREEN . BACK

The SCHID field.

This is the schedule ID that JOBB must be requested for if the job dependency is required. Here JOBB will only wait for JOBA3 if requested for a schedule ID of 3. If the field is left blank or zero is coded, the dependency will be for all schedule IDs. Note the schedule ID of JOBA3 is irrelevant.
Batch terminal example:
JOBCONN
UPD,JDEP,JOBB,OPT=A,SCHID=3,PRED=JOBA3
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The LEADTM field.

A 4 digit field but only values of 0 - 99 can be coded.
0 (default) means the JOB screen SATISFACTION LEAD TIME JOB value will be used. If this is 0 (default) it means that the requirement will be satisfied when JOBB enters the request queue if the start time of the last run of JOBA1 is after the start time of the last successful run of JOBB.
1-98 means the requirement will be satisfied if JOBA2 has run within that number of hours and since the last time JOBB started its last successful run.
If 99 is coded the requirement will not be satisfied when the job enters the request queue because of any previous runs. It will only be satisfied when the job completes after JOBB has been requested.
Batch terminal example: 
JOBCONN
UPD,JDEP,JOBB,OPT=A,PRED=JOBA2,LEADTM=12
THIS LINE TO TOP OF SCREEN . PREVIOUS SECTION . NEXT SECTION . JOB REQUIREMENT SCREEN . BACK

The NEXT-RUN field.

YES - the dependency will always occur (default). SKIP (can only be defined with OPT=U) - the dependency will not apply until there has been a successful run of JOBB. ONLY can only be defined with OPT=A. It means the dependency is deleted when JOBB next completes successfully.
Batch terminal example: 
JOBCONN
UPD,JDEP,JOBB,OPT=A,PRED=JOBA3,NEXTRUN=SKIP