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

MONITOR EVENT
Usage Notes
630 z/VM: CP Commands and Utilities Reference
USER USERID userid
specifies a list of users to be enabled or disabled in the USER domain. userid is
a list of one or more user IDs, separated by blanks.
EVent BLock m
specifies the maximum number of 4 KB pages, m, of the shared segment
(saved segment), that are accumulated before the virtual machine is notified
that the event data is available for data collection. You can modify m using the
MONITOR EVENT BLOCK command while event monitoring is active.
EVent STOP
deactivates the event-driven data collection. The monitor event profile is not
affected by this command, except for PARTITION, which is set to zero.
Note: Do not use this command to stop the MONWRITE utility. (See
“MONWRITE” on page 1853 for more information.)
EVent STArt
starts event monitoring for the domains and their elements listed in the event
profile set by the preceding MONITOR EVENT commands.
If no virtual machine is connected for event data (or no virtual machine
connected for event data has an active path to *MONITOR) when the command
is issued, event recording is held pending.
When recording is activated (that is, when there is a user connected with an
active path for event data), event configuration records from the monitor domain
are the first event records generated.
BLOCK m
specifies the maximum number of 4 KB frames of the shared segment, that
are accumulated before the virtual machine is notified that the event data is
available for data collection. The BLOCK value may be modified using the
MONITOR EVENT BLOCK command while event monitoring is active.
PARTITION n
specifies the number of 4 KB pages in the shared segment to be reserved
for event records. The rest of the shared segment is used for sample data.
EVENT CONFIG LIMIT n MINutes
EVENT CONFIG LIMIT n SEConds
specifies the time limit a user can refer to the event configuration area before
the data is refreshed or zeroed.
EVENT CONFIG SIZE n
specifies the size in 4 KB pages to be allocated in the saved segment for
EVENT configuration records.
(General)
1. Both event and sample monitoring can be active at the same time. The
MONITOR EVENT START command starts only event monitoring. To start both
event and sample monitoring, see “MONITOR START/STOP” on page 643.
Similarly, MONITOR EVENT STOP, stops only event monitoring while
MONITOR STOP stops both event and sample monitoring.
2. The following must be done to activate event recording:
v A saved segment must be defined and saved for the monitor
v A virtual machine must load the monitor saved segment and connect to
*MONITOR for event data
v A MONITOR START or MONITOR EVENT START command must be issued.