DB.3.2 - Job Predecessors Panel

Defining Requirements › Predecessor and Successor Definition › DB.3.2 - Job Predecessors Panel

DB.3.2 - Job Predecessors Panel

The DB.3.2 - Job Predecessors panel lets you establish predecessor job requirements.

To display the panel, enter:

2 as the FUNCTION on the DB.3 Menu panel.
3.2 as the FUNCTION on the DB Menu panel.
DB.3.2 as the FUNCTION value on any other menu or formatted input panel.
DB.3.2 or JOBCONN,JOB as a top line command.

To exit the panel:

Press PF3 to return to the DB.3 Menu panel except with the TSO-ISPF interface when PF3 has been assigned to another function.
Move the cursor to the top line of the panel and enter the wanted top line command if yet another function is wanted.

------------------------ CA-7 CPU JOB PREDECESSORS ------------------------- FUNCTION: xxxxxxxx (FORMAT,LIST,UPD) PAGE nnnn PRED FOR JOB: xxxxxxxx LIST-SCHID: nnn OPT SCHID LEADTM PRED-JOB NEXT-RUN x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx x nnn hhhh xxxxxxxx xxxx OPTIONS: A=ADD,D=DELETE,U=UPDATE,*=PROCESSED,?=ERROR PROGRAM: SM61 MSG-INDX: nn -- DB.3.2 -- yy.ddd / hh:mm:ss MESSAGE:

This panel contains the following fields:

FUNCTION

Specifies the function to perform. The value must be the name of some other panel or one of the following:

FORMAT: Clears the panel of user input data.
LIST: Lists data from the database. In batch, a formatted panel is not listed; only a found or not found message is returned.
UPD: Updates predecessor job requirements in the database according to OPT field values.

Batch keyword: Positional parameter

n/a

Predecessor type. Contains a constant value of JOB for jobs.

Limits: Required for batch only.

Batch keyword: Positional parameter

PRED FOR JOB

Specifies the job name for which job requirements are being defined or listed.

Limits: 1 to 8 alphanumeric characters

Batch keyword: Positional parameter

LIST-SCHID

(Optional) Applies only to the LIST function. A SCHID of 0 applies to connections for all schedules and therefore is listed with connections for any schedule ID requested. Schedule IDs on each detail line apply to that line only.

Default: Null (all connections for all schedule IDs appear)

Limits: 1 to 3 numeric characters from 0 through 999

Batch keyword: Not applicable

OPT

(Optional) Used with the UPD function, denotes the type of connection operation. The operation codes are A (add), D (delete), and U (update).

Note: The U option applies only to the LEADTM and NEXT-RUN fields.

Batch keyword: OPT

SCHID

(Optional) Specifies for which schedule ID (of this job, not the PRED-JOB) the requirement is applied. If omitted when the connection is made, default is 0. A zero default cannot be specified for one connection and a nonzero schedule ID used for another connection to the same job with the same predecessor job. An attempt to make such a connection results in an error message issued by CA WA CA 7 Edition. (For the online LIST function, the field on the same line as JOB field defaults to null causing all schedule IDs to be listed.)

Default: 0 (specifies the requirement holds for all schedule IDs)

Limits: 1 to 3 numeric characters from 0 through 999

Batch keyword: SCHID

LEADTM

(Optional) Specifies satisfaction lead time in hours. If nonzero, this value overrides any satisfaction lead time indicated on the DB.1 panel for this job connection. Values are the following:

0: Specifies that the predecessor job must have started and completed successfully since the last run of the dependent job. The amount of time that may have elapsed has no special consideration.
99: Specifies that the requirement is never considered initially satisfied when this job enters the request queue. The dependent job must complete typically while this job is in the request queue.
nn: Specifies that since the last run of this job, the predecessor job has started and completed successfully within the last nn hours. Values for nn can be 1 to 98.

Default: 0

Batch keyword: LEADTM

PRED-JOB

Names the job on which the job specified in the JOB field is dependent. This predecessor job name can be preceded by a slash (/) to indicate a negative job dependency. A conditional job dependency is indicated by prefixing the predecessor job name with a question mark (?). If job A is conditionally dependent on job B, then job A will depend on job B only if job B is in the request, ready, or active queues when job A enters the request queue.

If a generic negative dependency is specified, the successor job will only be submitted when there are not any jobs are submitted that meet the generic PRED-JOB criteria. If a generic dependency is defined without the slash, the successor job will enter the request queue with the generic requirement. The first job that completes and meets the generic PRED-JOB will satisfy that requirement. (CA WA CA 7 Edition produces a warning message indicating that PRED-JOB is not found.) Conditional dependencies cannot be specified as generic.

Limits: 1 to 9 alphanumeric characters
(or 1 to 8 alphanumeric characters terminated with an asterisk to indicate a generic name)

Batch keyword: PRED

Note: A job predecessor requirement defined as conditional (?) is considered satisfied if it is NOT in the request, ready, or active queue when the requiring job enters the request queue. Otherwise, the predecessor job is considered an unsatisfied requirement. Also, a conditional requirement can establish only one requirement per job even if multiple occurrences are in the queues for the other job.

A negative job dependency reflects mutual exclusion of jobs and prevents them from executing simultaneously. To ensure exclusion, a similar connection must also be made to define this job as mutually exclusive for the predecessor job. Lead time is not valid with negative job dependencies.

Negative job dependencies are checked when a job is in the ready queue preparing for submission (all other job requirements have been satisfied). If one of the job's mutually exclusive jobs has been submitted (ready queue or active queue), then a positive job dependency is assigned to the job and it is moved back to the request queue. The job will then wait for the successful completion of the mutually exclusive job before it will be ready for submission. A job requirement is assigned even if the active job was requested with a RUN function or command. The completion of the active job from RUN does not POST the requirement; the requirement must be posted manually.

NEXT-RUN

(Optional) Specifies status of this predecessor for the next run of this job. The next time that the job is scheduled into the queues, the following values determine the predecessors for that execution:

YES: Specifies normal, recurring predecessor.
ONLY: Specifies one-time predecessor for only the next run of this job. Automatically discarded by CA WA CA 7 Edition when next successful job completion is done. (See note.) Noted on QM.2 display as O and on several general inquiry displays as ONLY.
SKIP: Specifies normal, recurring predecessor that is to be skipped (ignored) when the next run is scheduled into the queues. Only valid when OPT=U and previous value was YES. Automatically reinstated to YES when next successful job completion is done. (See note.) Noted on certain displays as SKIP but does not appear on QM.2 displays since it is skipped when the job enters the queues.

Default: Yes (for OPT value of A)

Batch keyword: NEXTRUN

Note: The next successful job completion only applies to jobs that are not already in the queue when the NEXT-RUN is set. However, if the job is already in the queue and entered the queue when the NEXT-RUN was SKIP or ONLY, then it is reset as indicated.