Monitoring the system

In order to gather problem determination and performance information, you need to monitor the status of the system on a regular schedule. For example, to determine if you should start an extra message region, you might monitor the status of the queues during peak load.

You can determine the current status of the system by issuing /DISPLAY STATUS or QUERY commands, specifying the appropriate keywords. You can monitor the status of the IRLM by using the z/OS® command MODIFYirlmproc,STATUS.

You can use traces enabled by commands such as /TRACE, UPDATE TRACE (type-2 trace tables), UPDATE TRAN, and UPDATE MSLINK to help diagnose system operation problems. These commands turn on or off various IMS traces, which record use of IMS control blocks, message queue and I/O line buffers, save area sets, and MSC links.

IMS records trace information on the IMS log unless you request that the traces be recorded on an external trace data set. You can also use the /TRACE command to trace locking activities and to start and stop the IMS monitor.

You can use the IMS Monitor user exit (IMSMON) to access IMS Monitor data for your own performance monitoring tool or utility.

You can use the Operations Manager (OM) audit trail log to see the commands, the command responses, and the selected system messages that are routed through OM. When OM audit trail logging is enabled, the OM audit trail log is saved to log stream in the z/OS System Logger, as specified on the AUDITLOG= keyword of the IMSPLEX parameter in the OM initialization parameters PROCLIB member (CSLOIxxx). You can use TSO SPOC to view the OM audit trail log.