Job actions

The following are the different actions that you can define for Control-M to perform, based on various Job run events, such as conditions and Job status:

• Creating an Out Condition: Enables you to create an Out Condition that is added or deleted to the Conditions table when Job ends OK for a predecessor Job.
• Creating notifications: Enables you to create notifications that are sent to Alerts Window, Control-M/Server log file, User Console, or any defined location the Shout destination management in response to problems or integrating with other external monitoring applications. You can write the message, and set the urgency to Regular, Urgent, or Very Urgent. There are two types of notifications:
  • Notifications before Job's completion options: Notifications are based on various time. For example, Jobs not being submitted by a certain time, or a Job's average execution time is, or the Job is not finished by a certain time.
  • Notifications after Job's completion options: Notifications are based on a Job completing OK or Not OK.
• Creating On-Do Actions: Enables you to create automatic interventions, such as rerunning a Job or ordering a remedial Job, if a Job ends with a particular error code.

  Take into consideration that some options might not appear in your properties pane, if they were not specified in the User View you applied.