Data recording and the IMS Monitor
The IMS Monitor records
performance-related data during execution of the IMS online subsystem. When a significant event
occurs within IMS, IMS passes relevant data to the IMS Monitor when activated. The IMS Monitor formats a record describing the event,
including the time stamps, and logs the event.
Activating and controlling the IMS Monitor
If you create a DFSDCMON member in the IMS.SDFSRESL data set, you do not need a DD statement in the IMS, DBC, or DCC procedures for the IMS Monitor because IMS dynamically allocates and deallocates the IMS Monitor data set. You start and stop the IMS Monitor with the /TRACE command.
Monitoring using the /TRACE command
In addition to starting and stopping the IMS Monitor, you can specify the types of events to be monitored using the /TRACE command. You can use the /TRACE command to monitor various activities.
Log data from the IMS Monitor
Due to how your IMS Monitor log data set is stored, you should process the log after you stop the IMS Monitor and before restarting it again.
I/O errors on the IMS Monitor log data set
If a permanent I/O error occurs on the IMS Monitor log data set, IMS stops the IMS Monitor and issues message DFS2202. In this situation, you cannot restart the IMS Monitor until you restart IMS because IMS does not close the IMS Monitor log data set until you shut down IMS.
Monitoring IRLM
You can use the MODIFY irlmproc ,STATUS command to obtain information about IRLM activity.
Tracing IRLM activity
The IMS Monitor does not collect IRLM trace activity. IRLM uses the z/OS® component trace (CTRACE) facility. You can use the TRACE CT command to run various types of sublevel traces.