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.

For subsystem NVS, the status can be one of the following:<br />

v Y subsystem NVS active<br />

v N subsystem NVS inactive<br />

v T subsystem NVS terminated<br />

v M subsystem NVS disabled for maintenance<br />

The fifth line of the response, DEVICE DETAILS, tells you the channel connection<br />

address (CCA = 01) <strong>and</strong> the address of the director-to-device connection (DDC =<br />

01). The channel connection address is the channel connection address at the<br />

channel control interface.<br />

The director-to-device connection (DDC) is the director-to-device connection at the<br />

control unit interface. The DDC can be used to identify the physical location of a<br />

device. Because the 3990 Models 3 <strong>and</strong> 6 can swap devices around, the CCA no<br />

longer has a one-to-one correspondence with the DDC. The DDC can be used to<br />

locate a physical device that had previously been swapped because of a<br />

suspended primary device in a duplex pair. When the real device is offline, or is<br />

connected via FICON, there is no DDC data, <strong>and</strong> hyphens (--) are displayed.<br />

The sixth line of the response, DUPLEX DETAILS, tells you about the duplex<br />

control operations for the DASD at the specified device number. 1800 is the real<br />

device number of the volume that is the other volume of the duplex pair. If the other<br />

volume could not be located, hyphens (--) are displayed. The full response above<br />

tells you the following:<br />

v The DASD at the real device number 1801 is the secondary device in the duplex<br />

pair.<br />

v The other device in the duplex pair is at 1800.<br />

v The duplex operation is active.<br />

If the specified DASD was the primary device in the duplex pair, Secondary would<br />

read Primary.<br />

In the above example, the status of the Dual Copy pair is Active duplex. Other<br />

status conditions that could be indicated here instead, would be Pending duplex or<br />

Suspended duplex.<br />

The seventh line of the response, PAV DETAILS, tells you whether the queried<br />

DASD is a Parallel Access Volume. If the device is a base Parallel Access Volume,<br />

as in the above example, the response indicates the number of alias volumes<br />

currently associated with that base. If the device is an alias Parallel Access Volume,<br />

the response indicates the real device number of the associated base:<br />

PAV DETAILS: Alias volume associated with base rdev<br />

If the queried DASD is not a Parallel Access Volume, then the PAV DETAILS line is<br />

not included in the response.<br />

The eighth line of the response, PPRC DETAILS, tells you the queried active<br />

Peer-to-Peer Remote Copy mode. In the above sample, xxxxxxx is one of the<br />

modes:<br />

v PRIMARY. The volume from which PPRC makes a copy.<br />

QUERY DASD<br />

v SECONDARY. The volume that maintains a consistent copy of the primary<br />

volume.<br />

v CASCADING INTERMEDIATE. The volume that can be both a PPRC primary<br />

<strong>and</strong> secondary volume, allowing a multi-hop operation. In a multi-hop operation,<br />

PPRC uses a primary volume to send to a secondary volume <strong>and</strong> that secondary<br />

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

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

Saved successfully!

Ooh no, something went wrong!