Scheduler triggers

You can set up a scheduler trigger when you create or edit a schedule.

A trigger is a text string that the IBM® EMM Scheduler can send when a run completes successfully or when a run fails. If you have a schedule that sends a trigger on completion, you can set another schedule to start a run when it receives that trigger.

All schedules receive all sent triggers, but a schedule initiates a run only if the trigger string matches the trigger string for which it is waiting. An unlimited number of dependencies between schedules can be created in this manner.

After you have created a trigger, it appears in a dropdown list of triggers in the scheduler user interface, which makes it easy to use again.

Trigger example

You can schedule a set of Campaign flowcharts to run at the same time by giving all of them the same trigger. You can also use triggers to cause a set of flowcharts to run in series, one after another.

The following example illustrates how to set up a series of flowcharts to run in a specified order.

Flowchart 1 is scheduled with a "Flowchart 1 run complete" trigger that is sent when the run completes successfully.

Flowchart 2 is scheduled as follows.

Start when a "Flowchart 1 run complete" trigger is received.

Send a "Flowchart 2 complete" trigger when the run completes successfully.

Flowchart 3 is scheduled to start when a "Flowchart 2 run complete" trigger is received.

About start triggers

A schedule that is set up with a start trigger begins to listen for a trigger as soon as it is created, regardless of its start date. However, the trigger does not override the start date. For example, if a schedule has a start date of December 12, 2010 and on December 5, 2010 it receives its start trigger, the run will not start until December 12, 2010.