|
|
|
|
|
Specifies prerequisite conditions to be added or deleted after the job completes.
Additional information |
Description |
|---|---|
Usage |
Optional |
Format |
The Out Condition parameter is composed of the Name, Date, and Sign sub-parameters. These sub-parameters are described below. |
Variable Support |
Yes. Variable system variables (but not other types of variables) can be specified as the entire value for this parameter. |
Alternate names |
|
Add/Remove the condition |
Indicates whether the specified condition is to be added (created) or deleted.
If the value of ODAT is $$$$ or ****, + cannot be selected. |
The In Conditions parameter makes the submission of the job dependent on the existence of one or more prerequisite conditions.
NOTE: A maximum of 99 prerequisite conditions can be specified for the Out Conditions parameter.
If the job completion status is OK, then, according to the option specified, the prerequisite conditions are added to or deleted from the Conditions/Resources table. The Out Conditions parameter is performed before the Add/Remove Condition parameter. Therefore, the Out Conditions parameter can be overridden by those of the Add/Remove Condition parameter. For examples, see Add/Remove Condition.
Prerequisite conditions
A prerequisite condition is a user-defined entity whose existence can be tested to determine whether a job should be submitted for execution.
You can specify that a prerequisite condition be added (that is, created) or deleted as part of the post-processing treatment of a job (using the Out Condition parameter and the Add/Remove Condition parameter).
Prerequisite conditions are used to define and implement job execution dependencies. A job containing an In Condition definition is not submitted for execution unless the specified In conditions exist. This permits job-to-job dependencies or job dependencies based on successful completion of a manual task (such as a file creation or a restore operation).
When created, each prerequisite condition is associated with a specific date. A date is also specified when testing for the existence of a prerequisite condition. Thus, the submission of a job can be made contingent upon the existence of a prerequisite condition created on a specific date. This enables you to specify jobs, for example, that depend on conditions created on the same day and that ignore conditions created on previous days.
A prerequisite condition can represent any user-specified situation. The following represent the kind of self-explanatory conditions for which a job may need to test:
Time stamp
NOTE: Not relevant in z/OS environments.
Inserting the @HHMMSS code into an Out condition name includes a time stamp (in hours, minutes, and seconds) that is resolved to the time that the job is entered in the Active Jobs database.
Future and past dates
You can use the Days Offset field to set a future or past date for an Out condition. Valid values for this field are a + (plus) or - (minus) sign, followed by a number from 0 through 999. The value in the field represents the number of days in the future, or in the past, relative to the actual order date.
For examples of prerequisite conditions, see In Condition.
Parent Topic |