Usually prerequisite conditions are used to establish job dependencies locally, so that they apply on the Control-M where they are defined. However, 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. For example, you can specify that jobs in Control-M servers in Rome and Paris begin executing only after successful completion of a job in Sydney.
Global conditions are similar to prerequisite conditions except that their name begins with a prefix that identifies the conditions as a global condition.
You define the following:
Control-M/Server searches for the creation of designated global conditions in From Control-Ms and identified global conditions are then copied To Control-Ms. When global conditions are deleted in From Control-Ms, they are automatically deleted in To Control-Ms. By designating the same Control-M installations as both From and To Control-Ms, you can create bi-directional flows (as opposed to From/To flows), so any addition or deletion of a global condition in any such installation always results in the automatic addition or deletion of the global condition in the opposite direction.
The following procedures describe how to create and delete global condition prefixes in the Global Conditions Prefixes manager:
For a Global Condition example, see Global condition example. For best practices, see Control-M Global Condition Prefixes - best practice.
For more information on setting up dependencies between jobs from different Control-M/Servers, see Connecting jobs from different Control-M/Servers.
Parent Topic |