RMI elapsed and suspend time
The RMI elapsed time and suspend time fields provide an insight into the amount of time that a transaction spends in the CICS® resource manager interface (RMI).
Figure 1 shows the relationship between the RMI elapsed time (field id 170 in group DFHTASK) and the suspend time (field id 171 in group DFHTASK).
The RMI elapsed time includes part of a period of dispatch and CPU time at the start. This period of time began before the RMI elapsed time. When the dispatch and CPU time ends, the RMI suspend time begins. The RMI suspend time includes a dispatch wait at the end. When the dispatch wait ends, another period of dispatch and CPU time begins. Shortly afterwards, the RMI elapsed time ends, while the dispatch and CPU time continues. The RMI elapsed time therefore includes parts of two periods of dispatch and CPU time, with an intervening period of RMI suspend time.
The DB2® wait, the DB2 connection wait, and the DB2 readyq wait time fields, as well as the IMS wait and MQ GETWAIT wait time fields are included in the RMI suspend time.