Remote copy is not the same a duplexing. Try this
Q DASD DETAILS F52C
F52C CUTYPE = 2107-E8, DEVTYPE = 3390-0A, VOLSER = VTERES, CYLS = 3339
CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY
-SUBSYSTEM Y Y Y - N N
-DEVICE Y - - Y N N
DEVICE DETAILS: CCA = 2C, DDC = --
DUPLEX DETAILS: --
PPRC DETAILS: PRIMARY VOLUME
2007/3/12, Shimon Lebowitz <[EMAIL PROTECTED]>:
Hi,
I have a strange problem with some DASD.
The disks at 400-420 are used by MVS, and are
primaries in PPRC pairs (actually, HDS's HRC,
they are on a 9970 box).
MVS is running on a second system from VM,
but VM also has channel paths to that 9970,
and the IOCPs are identical, so both systems see
the same hardware setup.
Now, here is a sequence of operations that makes no
sense to me.
Q 400
DASD 0400 OFFLINE
READY; T=0.01/0.01 10:05:08
Q DUPLEX 400
HCPDMC1110E DEVICE 0400 IS NOT IN A DUPLEX PAIR.
READY(01110); T=0.01/0.01 10:05:13
VARY ON 400
0400 VARIED ONLINE
1 DEVICE(S) SPECIFIED; 1 DEVICE(S) SUCCESSFULLY VARIED ONLINE
READY; T=0.01/0.01 10:05:40
Q DUPLEX 400
HCPDMC332E INVALID CONTROL UNIT TYPE - 0400
READY(00332); T=0.01/0.01 10:05:49
#### I guess this makes sense, the CU is defined as 2105.
Q 400
DASD 0400
READY; T=0.01/0.01 10:05:52
#### Why doesn't VM see the VOLSER??
ATT 400 SYSTEM
HCPATM1117I DASD 0400 WAS NOT ATTACHED TO THE SYSTEM
BECAUSE IT IS THE SECONDARY IN A PPRC PAIR.
READY(01117); T=0.01/0.01 10:07:48
#### HUHHHH???????
ATT 400 *
DASD 0400 ATTACHED TO XMSL 0400 WITH DEVCTL
READY; T=0.01/0.01 10:09:29
TYPE Q400 DSF C
PPRCOPY QUERY UNIT(400)
READY; T=0.01/0.01 10:09:35
ICKDSF Q400 DSF C Q400 DSFLOG A
READY; T=0.01/0.02 10:09:54
#### The real volume is attached, so ICKDSF can see
the true PPRC status of the volume.
Q400 DSFLOG A1; F 133 BLKS=2 COL=2 REC=2 OF 39 FILES=1
====>
ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0 TIME:
10:09:54
PPRCOPY QUERY UNIT(400)
ICK00700I DEVICE INFORMATION FOR 0400 IS CURRENTLY AS FOLLOWS:
PHYSICAL DEVICE = 3390
STORAGE CONTROLLER = 3990
STORAGE CONTROL DESCRIPTOR = E9
DEVICE DESCRIPTOR = 0C
ADDITIONAL DEVICE INFORMATION = 4A001B35
ICK04030I DEVICE IS A PEER TO PEER REMOTE COPY VOLUME
QUERY REMOTE COPY - VOLUME
(PRIMARY) (SECONDARY)
SSID CCA SSID CCA
DEVICE LEVEL STATE PATH STATUS SERIAL# SERIAL#
------ --------- -------------- ----------- --------- -----------
0400 PRIMARY DUPLEX ACTIVE 9975 00 9905 00
33015 32387
PATHS SAID/DEST STATUS DESCRIPTION
----- --------- ------ ----------------
1 2002 0405 01 PATH ESTABLISHED
---- ---- 00 NO PATH
---- ---- 00 NO PATH
---- ---- 00 NO PATH
---- ---- 00 NO PATH
---- ---- 00 NO PATH
---- ---- 00 NO PATH
---- ---- 00 NO PATH
ICKDSF - CMS/XA/ESA DEVICE SUPPORT FACILITIES 17.0 TIME:
10:09:54
ICK02206I PPRCOPY QUERY FUNCTION COMPLETED SUCCESSFULLY
ICK00001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0
10:09:54 03/12/07
ICK00002I ICKDSF PROCESSING COMPLETE. MAXIMUM CONDITION CODE WAS 0
* * * END OF FILE * * *
#### ICKDSF clearly shows that this disk is a PRIMARY volume:
0400 PRIMARY DUPLEX ACTIVE 9975 00
9905 00
So, where is VM dreaming up that it is a SECONDARY?
Why can't I attach the volume to system??
Thanks!
Shimon
--
**********************************************************************
**
Shimon Lebowitz mailto:[EMAIL PROTECTED]
VM System Programmer .
Israel Police National HQ. http://www.poboxes.com/shimonpgp
Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308
**********************************************************************
**
--
Kris Buelens,
IBM Belgium, VM customer support
