Just as matter of recommended practice, putting a shared IODF cluster in a user catalog for the entire enterprise creates a huge dependency on that user catalog. The user catalog could go south (unlikely) or--worse--the shared IODF might get deleted by accident, making any IPL more or less wishful thinking.
Note that there is no enqueue on the IODF that was used for the current IPL. If it's gone, you might discover only on the next attempt to activate a new IODF dynamically. Or at the next IPL. ;-( . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Tom Marchant <[email protected]> To: [email protected], Date: 06/13/2014 09:55 AM Subject: Re: Dataset in Two master catalog Sent by: IBM Mainframe Discussion List <[email protected]> On Fri, 13 Jun 2014 08:52:06 -0500, Mark Zelden wrote: >On Thu, 12 Jun 2014 06:57:29 -0500, Dana Mitchell wrote: > >>During IPL, the master catalog is not used to locate the IODF, >>just name and device address. >> > >Umm... ever hear of dynamic activate? :-) The IODF must be cataloged on every >system unless you always want to IPL for even an MVS only change (like EDT). Right. I'm not sure what Dana's point was, but mine, when I posted something similar, was that it may be cataloged in a user catalog. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
