Conditions

Conditions are dependencies between Jobs. There are two types of conditions:

• In Condition: Specifies prerequisite conditions that must be satisfied before the Job is submitted for execution. The In Conditions parameter makes the submission of the Job dependent on the existence of one or more prerequisite conditions. To create an In Condition, see Create an In Condition. For more information about In Conditions, see In Condition in Parameters.
• Out Condition: Specifies prerequisite conditions to be added or deleted after the Job completes. For more information, see Out Condition in Parameters.

  An In Condition is usually associated with an Out Condition of a successful completion of predecessor Job.

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.

The Conditions management tool enables you to do the following:

• Monitor the active conditions that are in use.
• 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.

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.