Researching a delay in DB2 and CICS Using SYSVIEW
Article ID: 188423
Updated On:
Products
SYSVIEW Performance Management
Issue/Introduction
Researching a delay in DB2 and CICS, CICS TCB changes mode delay time.
This is causing 99% delay in the transaction and there is no explanation.
This is causing 99% delay in the transaction and there is no explanation.
Environment
Resolution
The CICS TCB change mode delay time is obtained from CICS monitoring field DFHTASK 247
(this can be found down farther in the transaction record under the DFHTASK section).
The IBM doc says:
247 (TYPE-S, 'DSCHMDLY', 12 BYTES)The elapsed time in which the user task waited for redispatch after a CICS Dispatcher change-TCB mode request was issued by or on behalf of the user task.
For example, a change-TCB mode request from a CICS L8 or S8 mode TCB back to the CICS QR mode TCB might have to wait for the QR TCB because another task is currently dispatched on the QR TCB.
This field is a component of the task suspend time, SUSPTIME (014), field.
(this can be found down farther in the transaction record under the DFHTASK section).
The IBM doc says:
247 (TYPE-S, 'DSCHMDLY', 12 BYTES)The elapsed time in which the user task waited for redispatch after a CICS Dispatcher change-TCB mode request was issued by or on behalf of the user task.
For example, a change-TCB mode request from a CICS L8 or S8 mode TCB back to the CICS QR mode TCB might have to wait for the QR TCB because another task is currently dispatched on the QR TCB.
This field is a component of the task suspend time, SUSPTIME (014), field.
Additional Information
For SYSVIEW PERFORMANCE considerations, see the IBM Document Performance Data in Group DFHTASK
Feedback
Yes
No
Powered by
