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.

Messages<br />

is the response for each 3990 Model 3 or 6 subsystem.<br />

If the cache is unavailable:<br />

v Destage is in progress is included in the response if the storage control is still<br />

in the process of moving changed data from the cache to the backing storage<br />

device.<br />

v If an error is encountered during the destaging process, destage has failed.<br />

Data is pinned. is displayed <strong>and</strong> the data that encountered the failure is held in<br />

the storage control cache.<br />

v Subsystem error is included if an internal subsystem error occurred which<br />

caused termination of caching.<br />

rdev CACHE {activated for device }<br />

{deactivated for device }<br />

{deactivation for device is pending.<br />

Destage has failed.}<br />

[rdev has pinned data]<br />

is the response for each device specified in the comm<strong>and</strong>; if pinned data exists for<br />

the device. The variables rdev, cccccccc, <strong>and</strong> aaaaaaaa are the same as in<br />

Response 1.<br />

pppppppp<br />

is the size in kilobytes of subsystem storage that is not available to the storage<br />

director for allocation because of DASD exception conditions which prevent<br />

successful completion of a subsystem storage to DASD transfer.<br />

Note: cccccccc, aaaaaaaa, oooooooo, <strong>and</strong> pppppppp are displayed in decimal.<br />

Response 2:<br />

{available }<br />

Bytes {unavailable} cannot be determined<br />

{offline }<br />

{bound }<br />

{pinned }<br />

is displayed if the storage control is unable to determine the subsystem storage<br />

capacity.<br />

H<strong>CP</strong>006E Invalid device type - {rdev|vdev|ldev}<br />

H<strong>CP</strong>009E Invalid range - range<br />

H<strong>CP</strong>021E A real device number was not supplied<br />

or it is invalid.<br />

H<strong>CP</strong>026E Oper<strong>and</strong> missing or invalid<br />

H<strong>CP</strong>040E Device {rdev|vdev|ldev} does not exist<br />

H<strong>CP</strong>296E Status is not as required - rdev; text<br />

H<strong>CP</strong>319E Error processing subsystem comm<strong>and</strong><br />

- cmd for DASD rdev<br />

H<strong>CP</strong>332E Invalid control unit type - rdev<br />

QUERY CACHE<br />

H<strong>CP</strong>1120E The requested<br />

[comm<strong>and</strong>|DETACH|GIVE] for device<br />

[ldev|rdev] did not complete in the<br />

allotted time.<br />

H<strong>CP</strong>1150E DASD {rdev|vdev} is not a valid base<br />

exposure.<br />

H<strong>CP</strong>2600I DASD rdev subsystem storage status<br />

cannot be determined.<br />

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

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

Saved successfully!

Ooh no, something went wrong!