Run dependency

You can set up a schedule to be dependent on successful completion of one or more other scheduled runs.

For example, suppose you have a schedule, S1, that is set up with a recurrence pattern. S1 has a trigger that is sent every time an S1 run completes successfully. Three schedules, S2, S3, and S4, are configured to start when they receive the outbound trigger from S1. You can set up an additional schedule, S5, that will run when S2, S3, and S4 complete successfully. S5 will run only when all three of the runs on which it is dependent complete.

To set up a scenario like the one described in the example, you would configure S5 using the On Completion of Other Tasks option in the When to Start drop down list.

When you configure a run to be dependent on other runs in this way, you must keep in mind the following considerations.

The schedules on which the schedule you are configuring depends must be non-recurring. In the example above, S2, S3, and S4 must be non-recurring. However, because S1 recurs, S2, S3, and S4 effectively recur, based on S1 runs.

The schedule that is dependent on other schedules must also be non-recurring. In the example, S5 must be non-recurring. Again, because S1 recurs, S5 effectively recurs as well.

The schedule that is dependent on other schedules cannot be used as one of the criteria in the On Completion of Other Tasks option for any other schedule. In the example, S5 cannot be used as a criterion in the On Completion of Other Tasks option for any other schedule.

If you want to delete a schedule that is configured with the On Completion of Other Tasks option, you must first change the configuration to remove the On Completion of Other Tasks option. Then you can delete the schedule.

Copyright IBM Corporation 2012. All Rights Reserved.