General Information

If the mission ends OK, the prerequisite conditions are added to or deleted from the IOA Conditions file according to the specified opt value.

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

To establish job or mission dependency, define a prerequisite condition in an OUT or DO COND statement in the job or mission that should run first, and in an IN statement in the job or mission that should run afterwards.
The job or mission containing a prerequisite condition in an IN statement is not submitted unless that prerequisite condition has been added manually or by a job or mission containing the OUT or DO COND statement.

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

The DO COND statement is used to add the prerequisite condition if the step/codes event criteria specified in the accompanying ON statement are satisfied.
If the IN condition can only be satisfied by manual intervention (for example, if TAPE1–LOADED is set by the operator after the loading a tape), performance of the required manual intervention before mission submission is ensured.

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

(For more information, see the description of parameter DO COND in this chapter.)

The following are examples of prerequisite conditions:

JOB_PAYCALC_ENDED_OK

PRINTER-SET

All prerequisite conditions are associated with a date reference that is used to distinguish between different runs of the same job or mission with different scheduling dates. If, for example, a condition is being deleted, only the condition matching the specified date is deleted. The same condition 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 following symbolic dates:

Table 232 Prerequisite Condition Symbolic Dates

Symbol	Description
STAT	Adds or deletes a prerequisite condition with the date value STAT.
ODAT	Adds or deletes the prerequisite condition with the original scheduling date of the job or mission.
PREV	Adds or deletes the prerequisite condition with the previous scheduling date of the job or mission (or ODAT–1 if the job or mission is being forced).
NEXT	Adds or deletes the prerequisite condition with the next scheduling date of the mission (or, for a forced mission, ODAT+1).
**** or $$$$	Valid only with an opt value of – . Either of these values results in the deletion of all matching prerequisite conditions regardless of date.

Prerequisite conditions created by parameter OUT can trigger the execution of other jobs or missions.

Prerequisite conditions deleted by parameter OUT can prevent the scheduling of jobs and missions that require those prerequisite conditions in their IN parameter.

For more information regarding prerequisite conditions, see Prerequisite Condition Concept.

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

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

Parent Topic

OUT: Post–Processing Parameter (decollating mission)