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.

The following response is also displayed if the real device is attached to the system<br />

for access as user minidisks or for system paging, spooling, or temporary disk<br />

space. This response is longer than the previous response because the device may<br />

be reserved (shared option is on), it may have a reserve pending, or it is currently<br />

reserved.<br />

q dasd active<br />

DASD 181A <strong>CP</strong> SYSTEM ESAP2C SHARED<br />

DASD 181B <strong>CP</strong> OWNED ESAP2F RESERVE PENDING FOR USER DAVID<br />

DASD 181C <strong>CP</strong> OWNED ESAP30 RESERVED BY SYSTEM<br />

Ready;<br />

Response 5:<br />

If the device is dedicated to a user, you see a message like this:<br />

q dasd<br />

DASD 0820 ATTACHED TO OLIVER 01FC R/0 XAUSR4<br />

Ready;<br />

This means the DASD at the real device number 0820 is attached to OLIVER’s<br />

virtual machine as the virtual device 01FC. The DASD’s volume identifier is<br />

XAUSR4. R/O means the user OLIVER has read-only access to the DASD. R/O<br />

might also read R/W, which means the user had read-write access. ATTACHED<br />

may be replaced with BOX/ATTC, which means that although the device is<br />

dedicated to a user, it is unavailable (usually because of a hardware condition).<br />

Response 6:<br />

If you enter QUERY DASD DRAINING, you see something like this:<br />

q dasd draining<br />

DASD Vol-ID Rdev Draining: PAge LInks SPool TDisk<br />

0C02 DR4209 0C02 Yes Yes Yes Yes<br />

0C04 DR5703 0C04 No No Yes No<br />

Ready;<br />

This response shows the device number <strong>and</strong> volume identifier of the DASD, as well<br />

as which operations are prevented on it. The second line indicates that <strong>CP</strong> will not<br />

write pages to the DASD at 0C02, allow LINK comm<strong>and</strong>s to minidisks on it, allocate<br />

space on it for new spool records, or allocate temporary disk requests on it. The<br />

third line indicates that <strong>CP</strong> will not allocate space for new spool records on the<br />

DASD at 0C04.<br />

Response 7<br />

If you enter QUERY DASD DETAILS <strong>and</strong> the device is attached to a noncaching<br />

storage control, you see the following response:<br />

rdev CUTYPE = cccc-mm, DEVTYPE = dddd-mm, VOLSER = vvvvvv, CYLS = nnnn<br />

If you enter QUERY DASD DETAILS for devices attached to a caching storage<br />

control (see Usage Notes), you see something like this:<br />

query dasd details 1801<br />

1801 CUTYPE = 3990-EC, DEVTYPE = 3390-06, VOLSER = USPK2, CYLS = 3339<br />

CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY<br />

-SUBSYSTEM Y Y Y - N N<br />

-DEVICE Y - - N N N<br />

DEVICE DETAILS: CCA = 01, DDC = 01<br />

QUERY DASD<br />

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

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

Saved successfully!

Ooh no, something went wrong!