The DB.3.2L - Job Predecessors panel lets you establish predecessor job requirements using long job names.
To display the panel, enter:
To exit the panel:
------------------------ CA-7 CPU JOB PREDECESSORS ------------------------- FUNCTION: xxxxxxxx (FORMAT,LIST,UPD) PAGE nnnn JOB/L: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx S: nnn OPT SCHID PRED-JOBL /LEADTM NEXT-RUN x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx x nnn xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx hhhh xxxx OPTIONS: A=ADD,D=DELETE,U=UPDATE,*=PROCESSED,?=ERROR PROGRAM: SM62 MSG-INDX: 00 -- DB.3.2L -- yy.ddd / hh:mm:ss MESSAGE: ENTER FUNCTION, TRANSFER OR ENTER A COMMAND ON THE TOP LINE
This panel contains the following fields:
Specifies the function to perform. The value must be the name of some other panel or one of the following values:
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 predecessor job requirements in the database according to OPT field values.
Batch keyword: Positional parameter
Predecessor type. Contains a constant value of JOBL for jobs.
Limits: Required for batch only.
Batch keyword: Positional parameter
Job name.
Limits: Required for batch only. Can leave blank.
Batch keyword: Positional parameter
Specifies the job name or long job name for which job requirements are being defined or listed.
Limits: 1 to 64 alphanumeric characters, case sensitive
Batch keyword: JOBL
(Optional) The LIST-SCHID field for this panel. 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
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 the LEADTM and NEXT-RUN fields.
Batch keyword: OPT
(Optional) Specifies for which schedule ID (of this job, not the PRED-JOBL) 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. (For the online LIST function, the field on the same line as JOB/L 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
(Optional) Specifies the satisfaction lead time in hours. If a nonzero, this value overrides any satisfaction lead time that is indicated on the DB.1 panel for this job connection. The following values are valid:
Specifies that the predecessor job must have started and completed successfully after the last run of the dependent job. The amount of time that has elapsed has no special consideration.
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.
Specifies after 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 through 98.
Default: 0
Batch keyword: LEADTM
Names the job on which the job specified in the JOB field is dependent. A slash (/) can precede this predecessor job name 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 depends on job B only if job B is in the request, ready, or active queues when job A enters the request queue.
Note: The generic dependencies are not permitted for the DB.3.2L screen. If you require generic dependencies, use the DB.3.2 screen to create the definition.
Limits: 1 through 65 alphanumeric characters
Batch keyword: DEPJOBL
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 the exclusion, make a similar connection also 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 is 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.
(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:
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 the note.) Noted on QM.2 display as O and on the various 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 the 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, it is reset as indicated.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|