The CMF performance class record provides detailed timing information
for each transaction as it is processed by CICS®. A transaction can be represented by one
or more performance class records depending on the monitoring options
selected. The key transaction timing fields are:
- Transaction response time
- Calculated by subtracting the transaction Start time from the
transaction Stop time. The transaction Start time and Stop time represent
the start and end of a transaction measurement interval. This is normally
the period between transaction attach and transaction detach but the
performance class record could represent a part of a transaction depending
on the monitoring options selected. See Transaction response time for
more information.
- Transaction dispatch time
- The elapsed time that the transaction was dispatched by the CICS dispatcher domain. See Transaction dispatch time for more information.
- Transaction CPU time
- The amount of processor (CPU) time used during the execution of
the task while it is dispatched. See Transaction CPU time for
more information.
- Transaction suspend (wait) time
- The total elapsed time that the transaction was suspended by the CICS dispatcher domain. This includes
all task suspend (wait) time including:
- The wait time for first dispatch (First Dispatch Delay). This
is then further broken down into:
- First Dispatch Delay due to TRANCLASS limits.
- First Dispatch Delay due to MXT limits.
- The wait time for redispatch (Dispatch Wait). This is the time
the transaction was still suspended but awaiting dispatch (wait for
redispatch) by the CICS dispatcher
domain.
- The total I/O wait and other wait times.
See Transaction suspend (wait) time for more information.
For detailed information on all the fields relating to the CICS dispatcher domain including
the CICS open transaction environment
(OTE), see DFHTASK fields.
The CMF performance class data also provides several other important
transaction timing measurements. They include:
- Exception wait time
- The accumulated time from all the exception conditions measured
by the CMF exception class records for the transaction. See CMF exception class data fields for more information on the CMF
exception class records.
- Program load time
- The total program fetch time (dispatch time, CPU time and DFHRPL
I/O wait time) for all programs invoked by the transaction that have
to be loaded into CICS program
storage from the DFHRPL program library. See Program load time for more information.
- Syncpoint elapsed time
- The total elapsed time that the transaction spent processing a
syncpoint. See Syncpoint elapsed time for more information.
The OTS indoubt wait time is the total elapsed time the transaction
spent indoubt whilst processing an Object Transaction Service (OTS)
syncpoint.
- RMI elapsed time
- The total elapsed time the transaction spent in all Resource Managers
(such as DB2®, IMS™ DBCTL, WebSphere® MQ)
invoked by the transaction using the CICS Resource
Manager Interface (RMI). See RMI elapsed and suspend time for
more information.
- JVM elapsed time
- The total elapsed time the transaction spent in the Java Virtual Machine (JVM) for all the CICS Java application
programs invoked by the transaction. See JVM elapsed and suspend time for
more information.
- JVM initialization time
- The elapsed time the transaction spent initializing the Java Virtual Machine (JVM) for all
the CICS Java application programs invoked by the transaction.
See JVM elapsed and suspend time for more information.
- JVM reset time
- The elapsed time the transaction spent resetting the Java Virtual Machine (JVM) for all the CICS Java application
programs invoked by the transaction. See JVM elapsed and suspend time for
more information.