Hello all Listers, thanks to all. I think I should let you guys know the outcome of this project.
With an IBM ROC helping me all afternoon yesterday, we finally conclued that it may be because of VM/ESA 2.30 is lecking maintenances to be able to handle the newer hardware (MP2003 and IBM 2105-F20 Shark). The VM was been instlled sometimes in October, 1998 and have no services applied to it since. Talking about stable - VM is the best. No matter how we twisted the IOCDS, we were getting the exact DISABLED WAIT PSW. We felt that when CP sends out the reset to all the channels when IPLed, it went into DISABLED WAIT because it does not understands the return code coming back from the channel/hardware. This is a great experience for me to be involved in the middle of a 'lack of planning', 'cold turkey' CPU upgrade project. They backs up the old O/S DASDs, shuts down the old system, rolls in and installs the new hardware, and starts restore. Hopefully the system would run just like in the new hardware. No parallel...no testing... Ummm..... We recommanded to upgrade to VVM 4.40 and try again. This time, I will do all the needed preparation before I drop in again. That is enough. I have been taken up a lot of the bandwidth in this List lately. Thanks again for all the help. You guys are the greatest! Regards, ...Roland --- "Roland P. Chung" <[EMAIL PROTECTED]> wrote: > Hi George, I have 5 CPOWNED volumes. I have used ICKDSF > to formated and DDR restored them all. The other 59 DASDs > are for user DATA. I just put a volume number on. > > The DISABLE WAIT PSW is 000A000000009025 - and the > explaination is; "SCP initialiated reset of the I/O > interface". Maybe something I should not have included in > the IOCDS? Let me check. > > Regards, > > ...Roland > > George Haddad <[EMAIL PROTECTED]> wrote: > If any ----- snipped ------
