General Information for DO COND

When a DO COND statement is activated, the specified prerequisite conditions are added to or deleted from the IOA Conditions file according to the value set for opt.

Prerequisite conditions are usually used to establish job dependencies or ensure manual intervention when required.

• To establish a job dependency, define a prerequisite condition in an OUT or DO COND statement in the job that must run first, and in an IN statement in the job that must run afterwards.

  The job containing a prerequisite condition in its IN statement is not submitted unless that prerequisite condition has been added manually or by the job containing an OUT or DO COND statement.

  An OUT statement is used to add the prerequisite condition if the job ends OK.

  Use a DO COND statement to add the prerequisite condition if the step and code event criteria specified in the accompanying ON statement are satisfied.

• If the IN prerequisite condition can only be satisfied by manual intervention (for example, TAPE1-ARRIVED is set by the operator after an external tape has arrived insight), performance of the required manual intervention before job submission is ensured.

OUT and DO COND statements can also be used to delete prerequisite conditions. The OUT statement of the job can be used to delete the prerequisite condition after the job ends OK. A DO COND statement can be used to delete prerequisite conditions if the accompanying ON step and code criteria are satisfied.

These statements are generally used to delete prerequisite conditions either to prevent a particular job from running or when the condition is no longer needed by any other jobs in the Active Jobs file.

DO COND functions are performed after the functions of the OUT parameter.

• If a prerequisite condition is added by the OUT parameter and deleted by the DO COND parameter, the combined effect is the deletion of the prerequisite condition.
• If a prerequisite condition is deleted by the OUT parameter and added by the DO COND parameter, the combined effect is the addition of that prerequisite condition.

  The following are examples of prerequisite conditions:

All prerequisite conditions are associated with a date reference that is used to distinguish between different runs of the same job with different scheduling dates. If, for example, a condition is being deleted, only the condition matching the specified date is deleted. The same condition associated with a different date is not deleted. When adding or deleting prerequisite conditions, the date associated with the prerequisite condition can be a specific 4-character date or one of the symbolic dates described in the explanation of parameter "dateref" in DO COND: Post–Processing Parameter.

Prerequisite conditions created by a DO COND statement can trigger the execution of other jobs or processes.

Prerequisite conditions deleted by a DO COND statement can prevent the execution of jobs and processes whose IN statements require those prerequisite conditions.

If two or more DO COND statements are contradictory, statements performed earlier are overridden by statements that are performed later.

For more information regarding prerequisite conditions, see IN: Runtime Scheduling Parameter, ON Statements: Post–Processing Parameter, and OUT: Post–Processing Parameter, and see Prerequisite Conditions.