|
|
|
|
|
The mission is activated only if all the prerequisite conditions (specified in the IN parameter) are satisfied.
A prerequisite condition can represent any user-specified situation. The following are a few examples of prerequisite conditions:
IMS-ACTIVE
WEEKEND
JOB-EJGH12-FINISHED
SALARY-OK
BRANCH_TRANSMISSION
Mission execution dependencies can be defined and implemented by using prerequisite conditions created by a DO COND statement. Prerequisite conditions can trigger (or stop) the activation of missions in Control-M/Analyzer and Control-D, and can also trigger or stop a job or process in Control-M.
Each prerequisite condition is associated with a specific scheduling date. This scheduling date differentiates between different activations of the same mission for different scheduling dates.
The PREV date reference automatically resolves to a scheduling date reference for the missions previous scheduling date.
The **** or $$$$ date reference can be any prerequisite condition with the same name as that specified in parameter IN, with any date reference that will satisfy the IN requirement.
The ODAT of an IN condition is only calculated once – when the mission is first ordered. This date is then retained until the mission is reordered.
Parent Topic |