Before or after a job completes, you can define one or more of the following different actions for a job to perform.
Out Conditions: Post-processing parameters that Control-M adds to the active environment only when the job ends. When a predecessor job ends, the addition of its Out conditions to the active environment enables successor jobs with the corresponding In conditions to run.
EXAMPLE: Job X has 3 In Conditions defined on an Order Date (A, B, and C) and 2 Out Conditions (D+, A-, B-, C-)
Job X starts running only if In Conditions A, B, and C on the Order Date are in the Conditions table. After Job X Ends OK, the Out Condition D is added to the Conditions table. Other jobs that are waiting for the condition as their In Condition, can start running, and A, B, and C conditions are removed from the Conditions table.
Notifications: Notifications that are sent to the Alerts Window, Control-M/Server log file, User Console, or any defined location in the Shout destination management in response to problems or integrating with other external monitoring applications. There are two types of notifications:
Notifications before job completion: Notifications based on the time of the job's submission and execution.
Notifications after job completion: Notifications based on a job completing OK or Not OK.
On-Do Actions: Automatic interventions, such as rerunning a job or ordering a remedial job, if a job ends with a particular error code. For more information, see Creating Notifications and On-Do Actions.
Capture from job output: Enables you to search the output of a job for specified text, and based on the capture parameters, extract words or characters from the output. For more information, see Defining the job capture criteria.
Output handling: Indicates how the job’s log file should be handled after the job ends with a status of OK. For more information, see Action.