Two weeks ago, I posted a question about VM giving incorrect information about disks.
> I did: > Q DASD DETAILS 400 > 0400 CUTYPE = 3990-E9, DEVTYPE = 3390-0C, VOLSER =, 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: -- > PPRC DETAILS: SECONDARY VOLUME > READY; T=0.01/0.01 14:31:46 > > As you see, VM still says: > PPRC DETAILS: SECONDARY VOLUME > which is in obvious contradiction to ICKDSF which says: > DEVICE LEVEL STATE PATH STATUS > ------ --------- -------------- ----------- > 0400 PRIMARY DUPLEX ACTIVE > > So, VM definitely has it wrong! :-( > Why??? and how do I get VM to see the light? Since no one here responded (except Kris, but not with an explanation or solution), I figured I should close the story by posting what I got from IBM. They don't know HOW it happened, but they said that somehow a bit in the RDEV got klobbered, resulting in VM being sure of one thing, when DSF (which actually asks the CU for the facts) knew otherwise. The solution was fairly simple: VARY OFF nnn SET RDEV nnn CLEAR VARY ON nnn The CLEAR did exactly that, cleared up the confusion. :-) Then I was able to ATTACH TO SYSTEM again, and all is well. 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 ********************************************************************** **
