General Information

The mission executes only if all the prerequisite conditions (specified in parameter IN) are satisfied.

A prerequisite condition can represent any user-specified situation. The following are a few examples of prerequisite conditions:

Morning-A-PRINTED

RESTORE-NEEDED

JOB-EJGH12-FINISHED

SALARY-DECOLLATED

Mission execution dependencies can be defined and implemented using prerequisite conditions. Usage of prerequisite conditions encompasses mission-to-mission or job-to-mission dependencies, or mission dependencies based on successful completion of a manual task (such as data entry or quality control).

A prerequisite condition can be created or deleted in various ways. For more information see the following:

• OUT: Post-processing Parameter
• Adding Conditions and Resources – The ADD Command
• Prerequisite Condition Concept

Each prerequisite condition is associated with a specific scheduling date. This scheduling date differentiates between different runs of the same mission for different scheduling dates.

The PREV date reference automatically resolves into a scheduling date reference for the mission’s previous scheduling date (or ODATE–1 for a forced mission).

The **** or $$$$ date reference indicates that any date is acceptable. Only the prerequisite condition name must match.