NIP does not look at COMMANDxx and that is where the duplicate volume issue is discovered.
The only way I know of to avoid the situation is to set the 'offline at ipl' switch on each unit for each LPAR. HTH and good luck -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Lizette Koehler Sent: Wednesday, November 12, 2008 12:25 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Devices online at IPL should be offline I have been racking my brain trying to remember how to do this (again). I have a series of replicated devices that should be offline at IPL. If they are not, then I get IEA213A DUPLICATE VOLUME which really annoys operations. In the IODEF they are defined as online. In my COMMNDxx they are defined as offline. I know that the message IEA213A is probably during NIP processing. So how to I ensure that NIP does not try to bring these devices online? My memory on this one is just swiss cheese. Lizette NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
