On: Tue, Nov 08, 2005 at 02:15:50PM -0600,Berry van Sleeuwen Wrote: } Kevin, } } The problem was not so much "it makes no sense" as it was a fault from the } hardware guys. The cable for 13 was plugged into the wrong director. The } directoraddress on director 1 points to the hardware where dasd VM2076 is } located. The same address on director 2 does point to the correct dasd, } address 3312 volser SU3312. So basically the address 3312 from VM points to } two different real disks. To 3312 on channel 10, 11 and 12. To 5312 (beeing } VM2076) on channel 13. Once the cable 13 was plugged into director 2 we only } saw 3312 even when we varried off all other paths. The IOCDS was/is still } correct. } } The problem now is that others say VM was at fault here for not reacting on } this error.
Nerry, VM does not consider that to be an error. VM believes what the hardware tells it, and there are some situations where your "error" is actually the desired condition. -- Rich Greenberg N6LRT Marietta, GA, USA richgr atsign panix.com + 1 770 321 6507 Eastern time zone. I speak for myself & my dogs only. VM'er since CP-67 Canines:Val, Red & Shasta (RIP),Red, husky Owner:Chinook-L Atlanta Siberian Husky Rescue. www.panix.com/~richgr/ Asst Owner:Sibernet-L
