Either change the OS Configuration or CLIP the old volumes to whatever convention you use for 'spare volumes'. Neither solution facilitates easy backout in case the system won't IPL far enough for you to log on a fix a problem. You could switch the IODF back to the old OS configuration, but you would still have duplicate volsers. Unless you have a another system to run CLIPs from, you're at risk.
We happen also to have performed DASD moves this weekend. We CLIPped the old ones. We had no problems. Used up all our votive candles however. ;-) . . JO.Skip Robinson SCE Infrastructure Technology Services Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Rob Schramm <[email protected]> To: [email protected] Date: 08/20/2012 09:34 AM Subject: Re: IPL sequence question Sent by: IBM Mainframe Discussion List <[email protected]> It would probably be better to change the configuration to have the "other copy" of the volumes come up OFFLINE=YES. Rob Schramm Senior Systems Consultant Imperium Group On Mon, Aug 20, 2012 at 7:23 AM, Salah Balboul <[email protected]> wrote: > During NIP and before COMMNDxx is processed > > Known as DASD "Pathing" phases: > > 1- Path testing > 2- Read device characters > 3- Self Describing product --> Msg IOS291I > 4- Volser processing --> This is the phase were duplicates are found. > > Execution of COMMNDxx happens during Master Scheduler Initialization phase of IPL "Last Phase". > > Thanks ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
