Thanks for that information, Alan.
2nd somewhat related question, we are paring up both VM and MVS volumes. My
MVS counterpart is doing the MVS volumes (under a z/OS partition), and I'm
doing the VM ones. When I issue the CP Q DASD DETAILS command on a MVS
volume known to VM, I get the following results:
q dasd details 400
0400 CUTYPE = 3990-EC, DEVTYPE = 3390-0C, VOLSER = DSMP01, CYLS = 10017
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 00, DDC = 00
DUPLEX DETAILS: --
When this volume is queried on MVS, it shows that it is the primary of a
duplexed pair. Why doesn't VM show this information also?
-----------------
Judson West
Teradata, a division of NCR Corporation
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
Sent: Monday, December 11, 2006 1:45 PM
To: [email protected]
Subject: Re: PPRC and R/W Minidisks
On Monday, 12/11/2006 at 12:04 PST, Judson West
<[EMAIL PROTECTED]> wrote:
> I am trying to establish a PPRC pairing and DSF says that it wants me to
> link R/W to the primary fullpack minidisks. What is DSF going to do with
> those fullpack minidisks?
Issue volume-related commmands to the disk controller, something only
possible with FP minis or dedicated devices. Metro Mirror (nee PPRC)
applies to an entire volume, not a minidisk.
> I am always nervous at these times...
But that's why you backed up the volume before you started down this path.
:-)
Alan Altmark
z/VM Development
IBM Endicott
