27.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

v A virtual machine must load the monitor saved segment <strong>and</strong> connect to<br />

*MONITOR for sample data<br />

v A MONITOR START or MONITOR SAMPLE START comm<strong>and</strong> must be<br />

issued.<br />

If the START comm<strong>and</strong> is issued when no virtual machine is connected with an<br />

active path to *MONITOR for sample data, sample recording is held pending<br />

until there is a connection with an active path.<br />

2. The intervals for sample data collection start at the time the sample start<br />

comm<strong>and</strong> is issued. Monitor does not generate sample records unless there is<br />

at least one eligible monitor user for sample data. The following are two<br />

examples for the condition mentioned above:<br />

v Example 1<br />

a. MONITOR SAMPLE START is issued at 10:00 A.M. with 10-minute<br />

intervals.<br />

b. A user connects to *MONITOR at 10:05 A.M. to collect sample data. The<br />

sample configuration records are generated at the connect time (10:05<br />

A.M.), <strong>and</strong> the first data records are generated at 10:10 A.M.<br />

v Example 2<br />

a. A user connects to *MONITOR at 10:00 A.M. to collect sample data.<br />

b. MONITOR SAMPLE START is issued at 10:05 A.M. with 10-minute<br />

intervals. The first sample data records are generated immediately after<br />

the sample configuration records are generated (at 10:05 A.M.). The next<br />

sample interval is at 10:15 A.M.<br />

3. It is possible for a user who connects to *MONITOR for sample data collection<br />

to receive two record notification messages—one for sample configuration<br />

followed by one for the sample data records. See 639 above.<br />

4. The sample configuration message might be delayed for a user who connects to<br />

*MONITOR to collect sample data, <strong>and</strong> in turn the sample data notifications are<br />

also delayed for the user.<br />

v If another user has already connected to *MONITOR to collect sample data<br />

<strong>and</strong> has not replied to the sample configuration message, the monitor<br />

regenerates the configuration records after the configuration area is free <strong>and</strong><br />

sends a sample configuration message to the user who just connected to<br />

*MONITOR.<br />

Note: If the MONITOR SAMPLE START comm<strong>and</strong> is issued before any user<br />

is connected to *MONITOR, the first user connected to *MONITOR<br />

holds the configuration area. When that user issues an IUCV REPLY<br />

or the configuration time limit expires, the other users who are<br />

connected receive data notification for a new set of configuration<br />

records.<br />

v If a user’s path to *MONITOR is quiesced (or at its IUCV message limit)<br />

when the sample configuration notification is sent, the user receives<br />

notification for a refreshed set of configuration records when he or she<br />

resumes his path (or responds to one or more previous messages).<br />

5. Both event <strong>and</strong> sample monitoring can be active at the same time. The<br />

MONITOR SAMPLE START comm<strong>and</strong> only starts sample monitoring. To start<br />

both event <strong>and</strong> sample monitoring, use the MONITOR START comm<strong>and</strong><br />

described in “MONITOR START/STOP” on page 643. Similarly, MONITOR<br />

SAMPLE STOP stops only sample monitoring while MONITOR STOP stops<br />

both event <strong>and</strong> sample monitoring.<br />

Specific Usage Notes for I/O:<br />

MONITOR SAMPLE<br />

Chapter 2. <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> 639

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!