Conditions management

Usually conditions are defined when creating a job in the Planning domain. A predecessor job creates a prerequisite condition upon completion that is required for a successor job to be submitted. For more information about conditions, see In Conditions and Job dependencies.

From the Tools domain, in the Conditions window, you can do the following:

• Monitor the active conditions that are in use.
• View the defined conditions when a job is executing, which are automatically deleted from the window after jobs have completed.
• Create conditions.

  You can add a condition in the Conditions window when a job depends on a condition that does not apply to other jobs. Not all prerequisite conditions are added by jobs. When Control-M must know the status of something outside its control, you can add a manual condition to notify Control-M of the status. To add a Condition, see Creating a condition

EXAMPLE: A backup job might require that a tape be physically loaded on a tape drive before the job can be submitted. To handle this, you can define in the job processing definition an In prerequisite condition (such as Tape Loaded) that is not added by another job, but rather, manually, by the operator, after physically loading the tape drive.

• Filter the display criteria.

  Each condition includes information such as the name, order date of the conditions and Control-M Server.

  NOTE: If you select Auto Refresh, the Conditions window is automatically refreshed.