z/VM: CP Commands and Utilities Reference - z/VM - IBM

MONITOR
Purpose
Usage Notes
Use the MONITOR commands to control the selection, collection, and reporting of
data from the host system:
v MONITOR EVENT controls monitoring of event data
v MONITOR SAMPLE controls monitoring of sample data
v MONITOR START starts both event and sample monitoring
v MONITOR STOP stops all monitoring.
(General for MONITOR)
1. MONITOR commands can be run from virtual machines with the A/E privilege.
In order to avoid conflict among the commands, the administrator should be
aware of the virtual machines that have the privilege to run the monitor
commands.
2. MONITOR START can be issued before or after a user connects to *MONITOR.
If the MONITOR START command is issued before any connection to
*MONITOR, monitor recording goes into a pending state until a user connects to
*MONITOR. The following must be done before the monitor recording gets
activated:
v A saved segment must be defined and saved for the monitor
v An application program running in a virtual machine must load the monitor
saved segment and connect to the *MONITOR CP system service
v A MONITOR START command must be issued.
3. Both the event and sample profiles can be changed after monitoring has
started. Note that:
v Partition size of the saved segment cannot be changed unless event
monitoring is stopped.
New event domains are activated upon completion of the EVENT command,
and new sample domains are activated when the next interval elapses.
4. For a detailed description of data collected, refer to the monitor records in z/VM:
Performance.
5. The valid classes and types for use with Seeks and I/O domains are listed in
the following table:
Table 16. Valid Classes and Types for Seeks and I/O Domains
CLASS TYPE Other TYPES Included Valid for Seeks Valid for I/O
3480 X
3490 X
3590 X
3380 X X
3390 X X
9336 X X
FB-512 1
9336 X X
SPOOL 1403 X
3203 X
3262 X
3505 X
MONITOR
Chapter 2. CP Commands 623