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

Responses
Notes:
a. To determine the number of pages currently designated for event
configuration records, enter the QUERY MONITOR EVENT command.
b. To reserve a number of pages for the event configuration area, enter the
MONITOR EVENT CONFIG SIZE command. If the MONITOR EVENT
CONFIG SIZE command has not been issued when the MONITOR EVENT
START command is issued, 68 pages are reserved for event configuration
recording, and the PARTITION size must be at least 76 pages.
3. The maximum PARTITION size depends on whether sample monitoring has
already been started, and on whether any user is connected to *MONITOR
when the command is issued to start event monitoring.
If sample monitoring has not started, and:
v If one or more users are connected, the maximum PARTITION value that can
be entered is the number of pages in the first type SC range of the saved
segment that is currently being used by monitor.
v If there are no users connected to *MONITOR, the maximum value for
PARTITION is equal to the maximum number of pages that can be specified
as a type SC range with the DEFSEG command.
If sample monitoring has been started, the maximum number of pages that can
be specified by PARTITION is reduced by one more than the number of pages
reserved for sample configuration records. (QUERY MONITOR EVENT or
QUERY MONITOR SAMPLE displays the number of pages currently reserved
for the event and the sample configuration areas.)
4. When monitoring is stopped, the value of PARTITION reverts to the default
value.
The command MONITOR EVENT START can be issued before or after a user
connects to *MONITOR to collect event data.
Response 1:
MONITOR EVENT STARTED -- RECORDING IS ACTIVATED
- or -
MONITOR EVENT STARTED BY [userid] -- RECORDING IS ACTIVATED
As a result of the MONITOR EVENT START command, event monitoring has
successfully started. There is at least one user with an active path connected to
*MONITOR for event data collection.
This response is sent to the user that issued the command. If this user is not the
system operator, the response containing [userid] is also sent to the system
operator.
Response 2:
MONITOR EVENT STARTED -- RECORDING IS PENDING
- or -
MONITOR EVENT STARTED BY [userid] -- RECORDING IS PENDING
MONITOR EVENT
MONITOR EVENT START has been issued. Because there is no user with an
active path connected to *MONITOR for event data collection, event monitoring is
held pending. It shall remain pending until the first user is connected to *MONITOR
for event data collection.
Chapter 2. CP Commands 633