│ │ │ │ │←─────────────────RMI Elapsed Time──────────────────→│ │ ↑ ↑ │ │ │ │ │ │ │←─────────────Suspend Time─────────────→│ │ Dispatch │ │ │ │ Dispatch and CPU │ │ │ │ and CPU ──────────┼────→│←───────────RMI Suspend Time───────────→│←─────┼────────── Time │ │ ↑ │ │ Time │ │ │ │ │ │ │ │←──Dispatch──→│ │ │ │ │ Wait │ │ │ │ │ │ │ │ │ │ │
When investigating performance problems relating to the CICS Resource Manager Interface (RMI) you will find it helpful in assisting your interpretation of the RMI timing fields if you have some knowledge of how CICS resource managers, such as DB2®, IMS™ (DBCTL), WebSphere® MQ, or user written, are being used by your CICS applications.
If an application invokes a CICS resource manager that in turn invokes another CICS resource manager from within the task-related user exit program (sometimes known as stacking RMIs) the CICS Resource Manager Interface (RMI) elapsed time field (RMITIME) will contain the total elapsed time from entry to exit of the first, or highest, level CICS resource manager.
For more detailed information on the timing fields for DB2 and IMS, see DFHDATA fields.
When investigating performance problems relating to the CICS Resource Manager Interface (RMI), you might also find it useful to read the following sections:
RMI other wait time:
The RMI other wait time contains the suspend (wait) time in the CICS dispatcher domain for other Resource Managers such CICS Sockets or user written.