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.

MONITOR SAMPLE<br />

1. Any overlapping of I/O devices can exist on a series of MONITOR SAMPLE<br />

comm<strong>and</strong>s on the I/O domain. For example, if the comm<strong>and</strong>:<br />

monitor sample enable i/o type 3380<br />

is followed by:<br />

640 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 enable i/o class dasd<br />

all DASD are enabled for monitoring. If the comm<strong>and</strong> is then followed by:<br />

monitor sample disable i/o type 3380<br />

monitoring ceases for all 3380 devices, but continues for all other types of<br />

DASD.<br />

2. A message is issued for any specified device that does not exist.<br />

3. Devices that are enabled but are found to be offline are monitored when varied<br />

online. A summary message is issued indicating how many devices are enabled<br />

for monitoring, <strong>and</strong> how many are offline.<br />

4. The VOLUME oper<strong>and</strong> can be used only for volumes attached to the system,<br />

because <strong>CP</strong> associates a volume label to a device number only at the time it is<br />

attached. If it is desired to enable a DASD not attached to the system, it can be<br />

done by using the DEVICE option.<br />

5. The volume to be monitored is maintained by its device address. Enabling or<br />

disabling a volume for monitoring remains valid as long as its device address<br />

does not change. For example, if a volume is detached <strong>and</strong> a volume with the<br />

same label at a different address is attached, the volume must be enabled<br />

again to be monitored, <strong>and</strong> its previous device address disabled.<br />

6. A cache data record will not be created for a secondary device of a duplex pair.<br />

Specific Usage Notes for INTERVAL:<br />

1. The valid range of values for INTERVAL is 6 to 3600 for SECONDS, <strong>and</strong> 1 to<br />

60 for MINUTES. INTERVAL values must be specified in whole numbers.<br />

2. The default value of INTERVAL is one minute (60 seconds).<br />

3. If an interval is currently in effect, the new interval does not take effect until the<br />

next sample data record is produced.<br />

4. The SAMPLE INTERVAL value must be greater than or equal to the SAMPLE<br />

RATE value.<br />

5. It is possible that data may not be reported by the time the interval expires. This<br />

happens when it takes longer than an interval to collect the data. If this<br />

happens, the interval time should be adjusted to allow sufficient time to collect<br />

<strong>and</strong> report the data.<br />

Specific Usage Notes for RATE:<br />

1. The valid range of value for RATE is .01 to 30 seconds. As many as two digits<br />

may be specified after the decimal point. Leading zeros are not required, <strong>and</strong><br />

trailing zeros are not required after the decimal point.<br />

2. The default value of RATE is two seconds.<br />

3. If a rate is currently in effect, the new rate does not take effect until the current<br />

high-frequency rate has elapsed.<br />

4. The SAMPLE RATE value specified must be less than or equal to the SAMPLE<br />

INTERVAL value.<br />

5. The frequency of doing high-frequency sampling is determined by the RATE<br />

setting, however the creation of monitor records containing high-frequency data<br />

is controlled by MONITOR SAMPLE INTERVAL.<br />

Specific Usage Notes for CONFIG SIZE:

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

Saved successfully!

Ooh no, something went wrong!