Events
Events create dependencies between jobs, which enables a successor job to execute after a predecessor job completes execution. After a predecessor job completes execution, an event is added in Control-M that enables any eligible jobs waiting for this event to run. The event is a prerequisiteThe part of the job definition that controls the flow of your jobs, such as an event that controls sequence or a resource that controls load required for a successor job to execute. However, a job cannot execute until all scheduling criteria and resource requirements are met.
The following image shows events between jobs:
In the Events Tool, you can monitor all the active events in your workflow, or filter specific information about an event, such as the date of an event. You can manually add an event, such as when a job depends on an event that is not added automatically.
If your database is down and you want to stop all the jobs in your workflow from accessing the database and executing, you can manually add an event to stop the jobs from accessing the database until the database is up and the jobs can continue executing.
The following video describes Control-M Events:
Creating an Event
This procedure describes how to create an event as a dependency between jobs, which enables the successor job to execute after the predecessor job has completed execution.
Begin
-
Hover over the predecessor job.
A triangle appears below the rectangle of the job.
-
Click and drag the triangle to the successor job.
The event appears between the two jobs. You can view the event information by clicking the triangle. The event attributes appear in the Prerequisites tab, as described in Event Attributes.
Wait for Event Attributes
The following table describes the Wait for Event attributes that a successor job must wait for before it can execute:
Attribute |
Description |
---|---|
Name |
Defines the name of the event. Rules:
By default, the event format is [Source Job Attribute: Job Name]-TO-[Target Job Attribute: Job Name]. This format can be defined in the Site Standard, as described in Defining the Event Format. |
Run Date |
Defines the date attribute associated with the event, as follows:
|
Delete |
Determines whether the event is deleted after the successor job completed execution. |
Relationship |
Determines the relationship between events where the successor is waiting for more than one event, as follows:
|
AND/OR |
Defines the relationship between the previous event and the successive event. |
Event Attributes
The following table describes the Event attributes added to a predecessor job after execution enabling the successor job to execute.
Attribute |
Description |
---|---|
Name |
Defines the name of the event. Rules:
By default, the format is [Source Job Attribute: Job Name]-TO-[Target Job Attribute: Job Name]. This format can be defined in the Site Standard, as described in Defining the Event Format. |
Run Date |
Defines the date when the event is added or deleted as follows:
|
Add/Delete |
Determines whether the event is added (default), or deleted from the job after it completed execution. |