General Information

When a DO COND statement is activated, the specified 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 and mission dependencies or ensure manual intervention when required.

To establish mission-to-job 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 its IN statement is not submitted unless that prerequisite condition has been added manually or by a job or mission containing an OUT or DO COND statement.

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

Statement DO COND adds the prerequisite condition if the identifying string specified in the accompanying WHEN statement is found.

If the IN prerequisite condition can only be satisfied by manual intervention (for example, PRINTER-SET is set by the operator after the printer is ready), performance of the required manual intervention before mission execution is ensured.

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

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.

(For more information, see the descriptions of parameters IN, OUT and WHEN later in this chapter.)

The following are examples of prerequisite conditions:

OSS-READY

WEEKEND

JOB_PAYCALC_ENDED_OK

PRINTER_SET

All prerequisite conditions are associated with a date reference that is used to distinguish between different executions of the same 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 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 following symbolic dates:

Table 209 Symbolic Prerequisite Condition Dates

Symbolic Date	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 mission.
PREV	Adds or deletes the prerequisite condition with the previous scheduling date of the mission (or ODAT–1 if the mission is forced).
NEXT	Adds or deletes the prerequisite condition with the next scheduling date of the mission (or ODAT+1 if the mission is forced).
**** 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 statement DO COND can trigger the execution of other jobs or missions.

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

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

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

Parent Topic

DO COND: Decollating Parameter (decollating mission)