Your DASD managers are the culprits. As I said in another post, this condition could persist for quite some time until an attempt to vary a duplicate volser online or to IPL.
. . 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 2:13 PM To: [email protected] Subject: (External):Re: IEA213A DUPLICATE VOLUME *** EXTERNAL EMAIL - Use caution when opening links or attachments *** Hi Robinson, Good to know the experience you were with. Ops has a enough time to reply the WTORs in those particular lpars. Those Volumes are 3400/3800/4800 strings, not all of volumes but some of ranges. I need to check with Storage if those has been CLIPped..... These messages started coming out from a few last IPL cycles, no messages until the last few IPLs which I think Storage made a change before. Possible solution would be that being allowed to indicate that in the case of a dup, either the HIGHER or LOWER address be put offline in IO Configuration part in IODF when a dup is encountered if the CLIPped is a necessity at their end. Thanks, Steve ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
