Catalog is not an issue (except that IODF should be cataloged somewhere), but location is. The PDS containing LOADxx must be on the same volume as the IODF. Let's call that IPLPARM. Sharing IODF means also sharing IPLPARM. It does not get edited very often, but putting it outside of GRS introduces some risk. If IPLPARM gets damaged, you're pretty much SOL for every system that shares it.
We have seven sysplexes. Almost nothing is shared across boundaries, including IODF and IPLPARM. . . . 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 jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Tuesday, February 17, 2015 11:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: Parallel Sysplex split >That's not true in our case. We share the IODF between two sysplexes, it is >cataloged in a user catalog that is connected to the master catalogs of all >systems in both sysplexes. For the purpose of the IPL, the IODF does not need to be cataloged at all. You designate the IODF volume via its unit address in the LOADPARM (pos. 1-4). The DSN of the IODF to be used is then specified in the LOADxx member (suffix specified via LOADPARM, pos. 5-6). The LOADxx member is searched in SYSx.IPLPARM (x=0, 1, ..., 9) or SYS1.PARMLIB on the IODF volume and finally in SYS1.PARMLIB on the IPL volume. No catalog is involved in all of this. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
