DFHDATA owns the following performance class data fields:
- 179 (Type-A, IMSREQCT, 4 bytes)
- The total number of IMS™ (DBCTL)
requests issued by the user task.
- 180 (Type-A, DB2REQCT, 8 bytes)
- The total number of DB2® EXEC
SQL and Instrumentation Facility Interface (IFI) requests issued by
the user task.
For more information on DB2 accounting and monitoring, see the CICS DB2 Guide.
- 186 (Type-S, IMSWAIT, 8 bytes)
- The total elapsed time in which the user task waited for IMS (DBCTL) to service the IMS requests issued by the user task.
For more information, see RMI elapsed and suspend time and Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (owner: DFHTASK, field ID:
014 and is also a component of the RMI suspend time field, RMISUSP
(owner: DFHTASK, field ID: 171).
- 187 (Type-S, DB2RDYQW, 8 bytes)
- The elapsed time in which the user task waited for a DB2 thread to become available.
For more
general information on DB2 accounting
and monitoring, see the CICS DB2 Guide.
For more
information, see RMI elapsed and suspend time and Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (group name: DFHTASK, field
ID: 014 and is also a component of the RMI suspend time field, RMISUSP
(owner: DFHTASK, field ID: 171).
- 188 (Type-S, DB2CONWT, 8 bytes)
- The value of this field depends on the version of DB2 to which CICS® is
connected:
- When CICS is connected
to DB2 Version 5 or earlier,
and is therefore not exploiting the CICS open
transaction environment (OTE), this field is the elapsed time in which
the user task waited for a CICS subtask
(TCB) to become available.
- When CICS is connected
to DB2 Version 6 or later, and
so is using the CICS open transaction
environment (OTE), this field is the elapsed time in which the user
task waited for a DB2 connection
to become available for use with the user tasks open TCB.
For more general information on DB2 accounting
and monitoring, see the CICS DB2 Guide.
For more
information, see RMI elapsed and suspend time and Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (group name: DFHTASK, field
ID: 014 and is also a component of the RMI suspend time field, RMISUSP
(owner: DFHTASK, field ID: 171).
For more general information
on the open transaction environment (OTE), see the CICS Application Programming Guide.
- 189 (Type-S, DB2WAIT, 8 bytes)
- The value of this field depends on the version of DB2 to which CICS is
connected:
- When CICS is connected
to DB2 Version 5 or earlier,
and is therefore not exploiting the CICS open
transaction environment (OTE), this field is the elapsed time in which
the user task waited for DB2 to
service the DB2 EXEC SQL and
Instrumentation Facility Interface (IFI) requests issued by the user
task.
- When CICS is connected
to DB2 Version 6 or later, and
so is using the CICS open transaction
environment (OTE), this field does not apply and is zero. This is
because the CICS-DB2 attachment facility uses open TCBs as the thread
TCBs rather than using specially created subtask TCBs and as a result
any waits in DB2 that occur
on a CICS L8 mode TCB will
not be visible to the CICS dispatcher
domain.
For more general information on DB2 accounting
and monitoring, see the CICS DB2 Guide.
For more
information, see RMI elapsed and suspend time and Transaction timing fields.
Note: This field is a component
of the task suspend time field, SUSPTIME (group name: DFHTASK, field
ID: 014 and is also a component of the RMI suspend time field, RMISUSP
(owner: DFHTASK, field ID: 171).
- 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 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.
This field should be added to the transaction CPU time field (USRCPUT)
when considering the measurement of the total CPU time consumed by
a transaction. This field will be zero for point-to-point messaging
activity, it will be non-zero where MQ API requests have resulted
in pub/sub (publish and subscribe) type messaging.