Execution of scheduled tasks in a data sharing environment

In a data sharing environment, all administrative task schedulers cooperate in the execution of scheduled tasks.

However, if a task has a member affinity (for example, if the db2-ssid parameter specifies the name of a Db2 member), only the administrative task scheduler that is associated with that Db2 member will execute the task. Therefore, if this administrative task scheduler is unavailable, the task will not be executed.

When a task has no member affinity (if the db2-ssid parameter is a null value), the first administrative task scheduler that is available executes the task. If the task execution can complete on this administrative task scheduler, other administrative task schedulers will not try executing this task. However, if the administrative task scheduler cannot start the execution, other administrative task schedulers will try to start executing the task until one succeeds, or all fail in executing the task. An administrative task scheduler is unavailable if its associated Db2 member is not running, or if all of its execution threads are busy.

You cannot predict which administrative task scheduler will execute a task. Successive executions of the same task can be done on different administrative task schedulers.