|
|
|
|
|
When a DO COND statement is specified, the designated prerequisite conditions are added to or deleted from the IOA Conditions file according to the specified opt value.
A prerequisite condition can define any user-specified situation. The following are examples of prerequisite conditions:
ACCT-IN-BALANCE
RESTORE-FILE-G0
SALARY-OK
Prerequisite conditions are the means by that the user can define and implement rule execution dependencies, including rule-to-rule dependencies or rule dependencies based on successful completion of a manual task (such as correction of errors).
Prerequisite conditions created by a DO COND statement can trigger (or stop) the activation of other rules or the execution of processes in Control-M, Control-D, and other environments.
Prerequisite conditions deleted by statement DO COND can stop the execution of rules, missions, and jobs that require those prerequisite conditions.
If the prerequisite condition to be added already exists, or the prerequisite condition to be deleted does not exist, the Control-M/Analyzer rule continues executing but returns the value 4 in system variable SYSRC.
Each prerequisite condition is associated with its specified date reference that identifies different runs of the same job on different scheduling dates.
If two or more DO COND statements contradict one another, the last executed statement overrides the preceding statements.
Control-M/Analyzer AutoEdit, System and Local variables can be embedded in the condition of a DO COND statement. These variables are resolved (replaced) at time of rule execution. For additional information on AutoEdit processing, see Control-M/Analyzer Variables.
Parent Topic |