Note that the prohibition against duplicate volsers affects only *online* volumes. It does not apply to volumes that simply happen to be physically/logically connected. If a volume is CLIPped to a volser matching one already online, there is no error posted at that time. This condition can last indefinitely until V ONLINE is attempted or an IPL in initiated. In the case of V ONLINE, the action will fail and require correction.
The insidious problem is attempting to IPL with dups. IPL will stop at each and every dup encountered. I've seen cases where an entire 'string' of DASD was overlooked in the final step of moving DASD volumes from one location to another. Unless you have an already running system to work from, Operator has to reply to IEA213A enough times to get past the dups. If the IPL needs to be restarted for any reason, then the same replies have to be reentered. I have suggested (without a formal requirement) that the installation be allowed to indicate that in the case of a dup, either the HIGHER or LOWER address be put offline when a dup is encountered. That would handle most cases well enough to get a running system. Meanwhile... . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Steve Lee Sent: Friday, November 20, 2020 9:42 AM To: [email protected] Subject: (External):Re: IEA213A DUPLICATE VOLUME *** EXTERNAL EMAIL - Use caution when opening links or attachments *** Thanks Mark. Steve ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
