Why tasks fail to get an initial dispatch
When a task is past the transaction class and MXT barriers, it can be attached to the dispatcher. It must then wait for its initial dispatch. If tasks are made to wait for a relatively long time for their first dispatch, you will probably notice the degradation in the performance of the system.
You can get evidence that tasks are waiting too long for a first
dispatch from performance class monitoring. If you do find this to
be the case, you need to investigate the reasons for the delay. To
calculate the initial dispatch delay incurred by a task use the following
fields from the performance-class monitoring record:
DSPDELAY = First dispatch delay
TCLDELAY = Transaction Class delay
MXTDELAY = MXT delay
Delay in dispatcher = DSPDELAY - (TCLDELAY + MXTDELAY)
If the value you calculate is significantly greater than 0, the dispatcher could not dispatch the task immediately.The following factors influence the length of time that a task
must wait before getting its first dispatch:
- The priority of the task
- Whether the system is becoming short on storage
- Whether the system is short on storage