Queue time delays: EQT + Delay Time = AQT

Effective Queue Time (EQT) is the time a job waits before an initiator considers it for selection. It is a measure of how long jobs are waiting for CPU resources - CPU resources might vary depending on the constraints in effect at the time. Actual Queue Time (AQT) is how long a job is in the queue before it is initiated.

Delays account for the difference between the EQT and AQT. More than one reason might account for a delay. ThruPut Manager AE attributes delay time to a single reason as long as that reason persists. Then any remaining delay time is attributed to the next reason. Here's a subset of the common reasons in "attributable order":

• JTS, User, DJC - These delays are user-initiated and are all techniques to delay a job starting until a trigger occurs to release them. Though these jobs have been submitted they do not age until the trigger occurs.
• Datacenter - These delays are datacenter-initiated and include systems offline, regular affinity delays, JAL errors and so on. Jobs age without restriction.
• Operations - These delays are Operations-initiated, such as when they place a HOLD on the job for some reason. The job continues to age through the hold.
• DFSMShsm Recalls- These delays occur when a job is waiting for recalls to complete. The job continues to age through the recall.
• Virtual Volume Staging - These delays occur when a job is waiting for recalls to complete. The job continues to age through the delay.
• Scheduling Environment - These delays occur when the job is waiting for the appropriate Scheduling Environment to become available. The job continues to age through the delay.
• Binding - These delays occur when the job is waiting for the appropriate combination of binding agents to become available. The job continues to age through the delay.
• DCS - These delays occur when a job is waiting for a data set that is held by another job. GS jobs do not age during this time. PS jobs do.

The area below the EQT line reflects how long jobs are waiting for CPU resources. The system was busiest at about 5:30. The area between the lines reflects the delays. Where the lines are close together, there is little delay; the greatest delays occurred at about 2:30.

Whatever the cause of the delay, if the job continues to age through the delays, then Serviced Delivered field reflects the where the AQT was with respect to the target, acceptable and critical thresholds. If the delay causes the job to stop aging, then the Service Delivered column reflects where the job would have been selected without that delay. For instance, if a GS job is held for data set contention (with a Target service time of 12 minutes) with a hold and releases it after 21 minutes and 2 seconds, and the job is initiated 31 seconds later, with no further delays, the EQT is 31 seconds, the AQT is 21 minutes and 33 seconds, the DCS delay is 21 minutes and 2 seconds, and the Service Delivered is at target.

Exceptional jobs have a value of Indeterminate in the Service Delivered field. For more information see Exceptional Jobs.

In the Job Summary Report Sample above, this job received service as a BNK QA Service Group; the service delivered is "before target"; there were two delays - 1 minute, 20 seconds for binding delay at queue time, and .01 seconds allocation at execution time.