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 EVENT<br />

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

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

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

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

Specific Usage Notes for CONFIG SIZE:<br />

1. The default size reserved for event configuration records when event monitoring<br />

is started is 68 pages.<br />

2. The MONITOR EVENT CONFIG SIZE can be issued only when event<br />

monitoring is not active. To change the size after event monitoring has been<br />

started, you must first stop event monitoring.<br />

3. The minimum value for CONFIG SIZE is one 4 KB page.<br />

4. The maximum value for CONFIG SIZE is equal to the maximum number of<br />

pages that can be specified as a type SC range with the DEFSEG comm<strong>and</strong>,<br />

minus 8 pages for event data records.<br />

Note: The number of pages reserved must fit within the saved segment to be<br />

used by monitor. This check is made when monitoring is started (if<br />

someone is connected to *MONITOR <strong>and</strong> the saved segment is known)<br />

or when the first user connects after monitoring has been started.<br />

5. The value of CONFIG SIZE is preserved when monitoring is stopped.<br />

Specific Usage Notes for CONFIG LIMIT:<br />

1. The CONFIG time limit is the amount of time a user can keep the configuration<br />

area in use.<br />

2. The CONFIG time limit default is 1 minute.<br />

3. The minimum value for CONFIG time limit is 1 second.<br />

4. The maximum value for CONFIG time limit is 120 minutes.<br />

5. The CONFIG time limit value must be specified as a whole number.<br />

6. When the CONFIG time limit expires, <strong>CP</strong>:<br />

v In the EXCLUSIVE environment–stops monitoring <strong>and</strong> issues message<br />

H<strong>CP</strong>6239I<br />

v In the SHARED environment–purges the configuration message, releases the<br />

corresponding saved-segment pages, <strong>and</strong> issues message H<strong>CP</strong>6253I. Data<br />

recording continues.<br />

7. Configuration records are created <strong>and</strong> the CONFIG time limit enforced<br />

whenever:<br />

v Recording has begun. (A MONITOR START comm<strong>and</strong> is issued <strong>and</strong> at least<br />

one user is connected, with an active path, for the type of monitoring being<br />

started.)<br />

v Recording is underway <strong>and</strong>:<br />

– A user connects (with an active path) for that type of monitor data<br />

– The path of a user connected for that type of data becomes active<br />

– The user, whose path to *MONITOR was quiesced when *MONITOR tried<br />

to send a configuration notification message, issues IUCV RESUME<br />

– The user, whose path to *MONITOR was at its IUCV message limit when<br />

*MONITOR tried to send a configuration notification message, issues<br />

IUCV REPLY or REJECT to one or more previous messages from<br />

*MONITOR.<br />

8. CONFIG time limit is preserved when monitoring is stopped.<br />

Specific Usage Notes for PARTITION:<br />

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

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

for event configuration records. The absolute minimum partition size is 9 pages.

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

Saved successfully!

Ooh no, something went wrong!