In Conditions

You define dependencies between jobs through the following:

• 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.

You can automatically create job dependencies by selecting a successor job, clicking and then connecting the successor job to the predecessor job. Both In and Out Conditions are automatically created. By default, the condition is deleted after the job ends, which eliminates clutter from active jobs even before the New Day process is run the following day. It is also useful if the job runs more than once (such as cyclic jobs or rerun jobs).

You can set job dependencies for jobs in the same Control-M/Servers or for jobs in different Control-M/servers.

• Connecting jobs from different Control-M/Servers: You can also define global prerequisites to establish job dependencies across different Control-M/Servers by defining condition name prefixes that indicate that a condition is global.
• Connecting jobs: You can define job dependencies between jobs of the same Control-M/Server.

EXAMPLE: A Job X has 3 In Conditions defined on an Order Date (A, B, and C).

Job X starts running only if In Conditions A, B, and C on the Order Date are in the Active Conditions list. After Job X Ends OK.