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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MONITOR START/STOP<br />

Responses<br />

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

*MONITOR <strong>CP</strong> system service<br />

v A MONITOR START comm<strong>and</strong> must be 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 event data, event recording is held pending until<br />

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

Specific Usage Note for BLOCK:<br />

1. The default BLOCK value is four 4 KB pages.<br />

2. The minimum value for BLOCK is four 4 KB pages.<br />

3. The maximum value for BLOCK is half the number of pages to be used for the<br />

event data area (partition-event config size).<br />

4. The value of BLOCK is saved when monitoring is stopped.<br />

Specific Usage Notes for PARTITION:<br />

1. The default PARTITION size is half the size of the saved segment. The<br />

minimum is nine pages.<br />

2. The minimum PARTITION size is eight pages plus the number of pages<br />

reserved for event configuration records.<br />

Notes:<br />

a. The QUERY MONITOR EVENT comm<strong>and</strong> can be used to display the<br />

number of pages currently designated for event configuration records.<br />

b. The MONITOR EVENT CONFIG SIZE comm<strong>and</strong> can be used to specify the<br />

number of pages to be reserved for the event configuration area. If the<br />

MONITOR EVENT CONFIG comm<strong>and</strong> has not been issued before the<br />

MONITOR START is issued, 68 pages are reserved for event configuration<br />

recording, <strong>and</strong> the PARTITION size must be at least 76 pages.<br />

c. The maximum PARTITION size depends on whether sample monitoring has<br />

already been started, <strong>and</strong> on whether any user is connected to *MONITOR<br />

when the comm<strong>and</strong> is issued to start event monitoring.<br />

If sample monitoring has not started, <strong>and</strong>:<br />

v If one or more users are connected, the maximum PARTITION value that<br />

can be entered is the number of pages in the first type SC range of the<br />

saved segment that is currently being used by the monitor.<br />

v If there are no users connected to *MONITOR, the maximum value for<br />

PARTITION is equal to the maximum number of pages that can be<br />

specified as a type SC range with the DEFSEG comm<strong>and</strong>.<br />

If sample monitoring has started, the maximum number of pages that can<br />

be specified by PARTITION is reduced by one more than the number of<br />

pages reserved for sample configuration records. (QUERY MONITOR<br />

EVENT <strong>and</strong> QUERY MONITOR SAMPLE display the number of pages<br />

currently reserved for the event <strong>and</strong> the sample configuration areas.)<br />

3. The maximum PARTITION size depends on whether sample monitoring has<br />

already been started, <strong>and</strong> on whether any user is connected to *MONITOR<br />

when the comm<strong>and</strong> is issued to start event monitoring.<br />

4. When monitoring is stopped, the value of PARTITION reverts to the default<br />

value.<br />

Response 1:<br />

644 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

MONITOR SAMPLE STARTED -- RECORDING IS ACTIVATED.

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

Saved successfully!

Ooh no, something went wrong!