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

MONITOR START/STOP
►►
MONitor
Authorization
Purpose
Operands
STArt
STOP
Usage Notes
BLock
BLock
4
m
Privilege Class: A, E
PARTition
n
Use the MONITOR START command to activate event and sample monitoring
based on the profiles established by the preceding MONITOR EVENT and
MONITOR SAMPLE commands or by either one of those commands.
Use the MONITOR STOP command to deactivate all monitoring.
MONITOR START/STOP
STArt
activates event and sample monitoring based on the profiles established by the
MONITOR EVENT and MONITOR SAMPLE commands. Event monitoring is
started first.
STOP
deactivates the event and sample monitoring. The profiles for event and sample
monitoring are not affected by this command, except for PARTITION which is
set to zero. Event monitoring is stopped first.
Note: Do not use this command to stop the MONWRITE utility. (See
“MONWRITE” on page 1853 for more information.)
BLock m
specifies the number of 4 KB frames, m, 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 frames, n, in the shared segment that are
reserved for event records. The rest of the shared segment is then used for
sample data.
1. The MONITOR START command can be issued before or after a user connects
to *MONITOR. If the MONITOR START command is issued and there is no
connection to *MONITOR through an active path, monitor recording goes into a
pending state. Monitor recording is not activated until there is a user connected
with an active path (a path that is not quiesced at its IUCV message limit).
The following must be done before monitor recording gets activated:
v A saved segment must be defined and saved for the monitor
►◄
Chapter 2. CP Commands 643