For CPU jobs, data set requirements are initially set by CA WA CA 7 Edition at initial job LOAD time. In other words, when a job runs for the first time, CA WA CA 7 Edition automatically connects the job's input data sets as requirements when the job completes. The top line LOAD command can also be issued to accomplish this.
The DB.3.1 - Data Set Predecessors panel lets you modify such requirements or to add data set requirements for data sets that are not used as input for the job.
To display the panel, enter:
To exit the panel:
------------------------ CA-7 DATA SET PREDECESSORS ------------------------ FUNCTION: xxxxxxxx (FORMAT,LIST,UPD) PAGE nnnn PRED FOR JOB: xxxxxxxx LIST-SCHID: nnn NEXT OPT SCHID LEADTM *-------------- DATASET NAME --------------* DSNBR PERM -RUN x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx x nnn hhhh xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx nnnnnnn x xxxx OPTIONS: A=ADD,D=DELETE,U=UPDATE,*=PROCESSED,?=ERROR PROGRAM: SM61 MSG-INDX: nn -- DB.3.1 -- yy.ddd / hh:mm:ss MESSAGE:
This panel contains the following fields:
Specifies the function to perform. Value must be the name of some other panel or one of the following:
Clears the panel of user input data.
Lists data from the database. In batch, a formatted panel is not listed; only a found or not found message is returned.
Updates a data set requirement according to OPT field values.
Batch keyword: Positional parameter
Predecessor type. Contains a constant value of DSN for data sets.
Limits: Required for batch only.
Batch keyword: Positional parameter
Specifies the required job name for which data set predecessors are being defined.
Limits: 1 to 8 alphanumeric characters
Batch keyword: Positional parameter
(Optional) Applies only to the LIST function. When used, all connections for the SCHID entered and all connections for schedule ID of 0 are listed. Schedule IDs on each detail line apply to that line only.
Default: Null (Causes connections for all schedule IDs to be listed).
Limits: 1 to 3 numeric characters
Batch keyword: Not applicable
(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 LEADTM, PERM, and NEXT-RUN fields.
Batch keyword: OPT
(Optional) Specifies for which schedule ID of this job the data set requirement is applied. The user cannot specify the zero default for one connection and use a nonzero schedule ID for another connection to the same job and data set. An attempt to make such a connection results in a CA WA CA 7 Edition error message. (For an online LIST function, the SCHID field on the same line as JOB field defaults to null, causing all schedule IDs to be listed.) This field cannot be changed with OPT=U.
Default: 0 (requirement holds for all schedule IDs)
Limits: 1 to 3 numeric characters from 0 through 999
Batch keyword: SCHID
(Optional) Represents satisfaction lead time in hours. If the value is nonzero, this value overrides any satisfaction lead time on the DB.1 panel for data sets. The following values are valid:
Specifies that the data set must have been created or updated after the start time of the last run of the job. The amount of time that has elapsed has no special consideration.
Specifies that the requirement is never considered initially satisfied when the job enters the request queue. The data set must be created or updated while this job is in the request queue.
Specifies that the data set must have been created or updated within the last nn hours. Values for nn can be 1 through 98.
Default: 0
Batch keyword: LEADTM
Defines the fully qualified data set name that is defined as a data set requirement for the job in the JOB field.
Limits: 1 to 44 alphanumeric characters and required unless DSNBR is used.
Batch keyword: DSN
Specifies the data set number (as previously assigned by CA WA CA 7 Edition) that is defined as a data set requirement for the job in the JOB field.
Limits: 1 to 8 numeric characters and required unless DSNAME is used.
Batch keyword: DSNBR
(Optional) Specifies whether to consider this data set permanent by CA WA CA 7 Edition for the requirements of this job (Y or N). The DB.6 panel can be used to mark a data set as permanent for all jobs. This field defines the data set as permanent only for this job.
Default: N
Batch keyword: PERM
(Optional) Specifies status of this predecessor for the next run of this job. The next time that the job is scheduled into the queues, this value determines the predecessors for that execution.
Specifies normal, recurring predecessor.
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.) Only valid when OPT=A. Noted on QM.2 display as O and on other general inquiry displays as ONLY.
Specifies normal, recurring predecessor that is 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 because 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.
Copyright © 2015 CA Technologies.
All rights reserved.
|
|