Performance data in group DFHDATA
Descriptions of the performance data fields in the DFHDATA group, including the numeric identifier, type, and size of each field.
For more information about the time measurements used in some fields in this group, see Clocks and time stamps.
For more information about the elapsed time spent waiting for I/O operations and the relationship of that time to other time periods recorded for the transaction, see Transaction wait (suspend) times.
- 179 (TYPE-A, 'IMSREQCT', 4 BYTES)
- The number of IMS (DBCTL) requests issued by the user task.
- 180 (TYPE-A, 'DB2REQCT', 4 BYTES)
- The total number of DB2® EXEC SQL and Instrumentation Facility Interface (IFI) requests issued by the user task.
- 186 (TYPE-S, 'IMSWAIT', 12 BYTES)
- The elapsed time during which the user task waited for DBCTL to
service the IMS requests issued
by the user task.
This field value is zero if IMS supports the open transaction environment (OTE).
Note: This field is a component of the task suspend time, SUSPTIME (014) field. - 187 (TYPE-S, 'DB2RDYQW', 12 BYTES)
- The elapsed time during which the user task waited for a DB2 thread to become available.
Note: This field is a component of the task suspend time, SUSPTIME (014) field.
- 188 (TYPE-S, 'DB2CONWT', 12 BYTES)
- The elapsed time during which the user task waited for a DB2 connection to become available
for use with the user task's open TCB. Note: This field is a component of the task suspend time, SUSPTIME (014) field.
- 395 (TYPE-A, 'WMQREQCT', 4 BYTES)
- The total number of WebSphere® MQ requests issued by the user task.
- 396 (TYPE-S, 'WMQGETWT', 12 BYTES)
- The elapsed time during which the user task waited for WebSphere MQ to service the user task's GETWAIT request.
- 397 (TYPE-S, 'WMQASRBT', 12 BYTES)
- The WebSphere MQ SRB
time this transaction spent processing WebSphere MQ API requests. Add this field
to the transaction CPU time field (USRCPUT) when considering the measurement
of the total processor time consumed by a transaction. This field
is zero for point-to-point messaging activity, but it is nonzero where WebSphere MQ API requests
result in publish and subscribe type messaging.Note: WebSphere MQ only returns this value to CICS® when Class 3 accounting information is being collected in WebSphere MQ; if this information is not being collected, the field is always zero. To start collecting Class 3 accounting information, issue the command
START TRACE(ACCTG) DEST(SMF) CLASS(3)in WebSphere MQ.