|
|
|
|
|
The report decollating mission processes the job’s reports only if all the prerequisite conditions specified in the IN statements are satisfied.
A prerequisite condition can represent any user-specified situation. The following are examples of prerequisite conditions:
WEEKEND
JOB-EJGH12-FINISHED
PRINTER-SET
Mission execution dependencies can be defined and implemented by 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 further information, see the description of the OUT and DO COND statements in this chapter, Adding Conditions and Resources – The ADD Command, and Prerequisite Condition Concept.
Each prerequisite condition is associated with a specific scheduling date. This scheduling date differentiates between different runs of the same report decollating mission for different scheduling dates.
The PREV date reference automatically resolves to a scheduling date reference for the report decollating mission’s previous scheduling date (or ODAT–1 for a forced mission).
The **** or $$$$ date reference indicates that any date is acceptable. Only the prerequisite condition name must match.
Parent Topic |