On Tuesday, 11/25/2008 at 11:43 EST, Mary Anne Matyaz <[EMAIL PROTECTED]> wrote: > Hello all. While we're on the subject of DASD today, I finally got my chpids to > access the production dasd from the > D/R machine z/VM 5.4 lpar. I tried to accept a big range, and maint hung up. I > waited a half hour, then tried to > force him. No joy. So I removed the dasd from the not accepted list, and IPL'd. > The IPL took 5 minutes to get to the > SALIPL Screen. When it came up, I tried to vary on a range of about 15 devices. > Again, hung up maint. Wait 1/2 hour, > IPL. Tried to vary on one device, and it worked! So I tried the next one, hung > up my ID, and it's still sitting there 45 minutes > later. > Any ideas? Some sort of MIH setting? The SDMPlex is fine...not a whole lot of > activity on these devices. I have 2 chpids > online. I understand it's going to be slower, but this just won't work. :)
I have always understood that channel extenders for DASD are not supported because of the latency. You should probably check the dasd control unit to see if it's logging any errors on its own. Is EREP showing anything? Alan Altmark z/VM Development IBM Endicott
