Job dependencies

Job dependencies defines how jobs are connected. A job is dependent on another job if it is defined to run only after the successful completion of another job.

For more information on dependencies, see the following:

• Connecting jobs: You can connect jobs from the same Control-M/Server, by clicking and dragging from one host to another in the flow diagram.
• 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, as described in Creating a Global Conditions Prefix.
• Creating an In Condition: You can set an In Condition, which establishes dependencies between jobs using logical operators such as And, Or, and parentheses, as in following:
  • If a job in a critical service is dependent on two jobs connected using the And operator, the time necessary for both jobs to complete determines when the critical service completes (meaning, the longest possible time for both jobs).
  • If a job in a critical service is dependent on two jobs connected using the Or operator, the time necessary for only one of the two jobs to complete determines when the critical service completes (meaning, the shortest possible time for one job).