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

- or -
MONITOR SAMPLE STARTED BY [userid] -- RECORDING IS ACTIVATED.
As a result of the MONITOR START command, sample monitoring has successfully
started. There is at least one user with an active path connected to *MONITOR for
sample data collection.
MONITOR SAMPLE STARTED -- RECORDING IS PENDING.
- or -
MONITOR SAMPLE STARTED BY [userid] -- RECORDING IS PENDING.
MONITOR START has been issued. Because there is no user with an active path
connected to *MONITOR for sample data collection, sample monitoring is held
pending. It shall remain pending until the first user is connected to *MONITOR for
sample data collection.
MONITOR EVENT STARTED -- RECORDING IS ACTIVATED.
- or -
MONITOR EVENT STARTED BY [userid] -- RECORDING IS ACTIVATED.
As a result of the MONITOR START command, event monitoring has successfully
started. There is at least one user with an active path connected to *MONITOR for
event data collection.
MONITOR EVENT STARTED -- RECORDING IS PENDING.
- or -
MONITOR EVENT STARTED BY [userid] -- RECORDING IS PENDING.
MONITOR 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.
Notes:
1. Only one of the above responses is displayed for sample monitoring; another is
displayed for event monitoring. Depending on the profile set up for monitoring,
one or the other, or both, will be displayed.
2. These responses are sent to the user that issued the command. If this user is
not the system operator, the responses containing [userid] are also sent to the
system operator.
Response 2:
MONITOR SAMPLE STOPPED
- or -
MONITOR SAMPLE STOPPED BY [userid]
As a result of the MONITOR STOP command, sample monitoring has been
stopped.
MONITOR EVENT STOPPED
- or -
MONITOR EVENT STOPPED BY [userid]
MONITOR START/STOP
Chapter 2. CP Commands 645