The search stops when the first dataset is found (SYS0 - SYS9.IPLPARM, then SYS1.PARMLIB). So if you have a SYSx.IPLPARM and a SYS1.PARMLIB on the IODF volume, SYS1.PARMLIB is not searched. If your LOADxx member is in SYS1.PARMLIB and not in your SYSx.IPLPARM, your IPL will fail. I would remove the SYS1.PARMLIB from the IODF volume.
Bill Choate -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Horein, Steve (HAR-ORL) Sent: Thursday, November 30, 2006 8:43 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Moving LOADxx Oy! So if LOADxx resides in SYSx.IPLPARM, but the load parm specifies LOADxy which is found in SYS1.PARMLIB, I fail?! -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Thursday, November 30, 2006 8:36 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Moving LOADxx <snip quoted text> Once you create SYSx.IPLPARM on the IODF volume, SYS1.PARMLIB will not be used. And BTW, the "x" in SYSx has to be 0-9. -- Tom Marchant ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
