General Information for IN

A job cannot be submitted unless all the prerequisite condition criteria specified in the IN statements have been satisfied.

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

• To establish 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 the OUT or DO COND statement.

  • An OUT statement adds the prerequisite condition if the job ends OK.
  • The DO COND statement adds 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 arrives on-site), performance of the required manual intervention before job submission can be ensured.

OUT and DO COND statements can also be used to delete prerequisite conditions that are no longer needed. If an IN prerequisite condition for a job is not an IN prerequisite condition for any other job, you can use the OUT statement of the job to delete the prerequisite condition after the job ends OK.

The following are examples of prerequisite conditions:

All prerequisite conditions are created with a date reference. When specifying a prerequisite condition as an IN condition, you must specify the date for the condition. Only a prerequisite condition with the specified date can satisfy the IN requirement.

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