You are making the issue more complicated than it should be. <g> Go ahead an move the LOADxx parm member into SYSx.IPLPARM. For testing purposes you could change the XX to some other suffix and use that for the system IPL. If you have a problem, you can change the LOAD parm back to the original LOADxx suffix.
SYSx.IPLPARM and the IODF file do not need to be cataloged. They usually are cataloged so you can find them. You could even use something other than SYS1 for the IPLPARM dataset, like SYS0. Then catalog that file in the same user catalog as the IODF, and create an alias pointer in each system master catalog. Once one system is running, you can then move the other system over. Then remove the LOADxx parms from their SYS1.PARMLIB datasets. On Wed, 29 Nov 2006 17:01:53 -0600, Steve Horein <[EMAIL PROTECTED]> wrote: >Maybe I have a new one for you all! >I would like to move LOADxx out of SYS1.PARMLIB and into SYSx.IPLPARM on the >IODF volume. Really no big deal, just do it, right? Well, no. I have 2 >LPARS, Production and Sandbox. At this time, SYS1.PARMLIB lives on the >Sysres for each system, and is directly cataloged to each system's Master >Catalog. The HLQ for IODF is in a User catalog shared by both systems. In >the Sandbox LOADxx, I'm testing and using '==' and '========' for IODF >suffix and IODF HLQ to get the IODF specification. In Production LOADxx, >these values are hard-coded. Is it possible to create a new IODF on a new >volume, naming it <MyHLQ>.IODFxx.&SYSNAME, where MyHLQ is the HLQ found in >the hardware configuration token? <MyHLQ>.IODFxx is the current IODF name. >I'm confused at what HCD help is telling me: > >"A production (or a work) IODF name can have a maximum >length of 35 characters. The first level qualifier can be >the TSO prefix (user ID). The second level qualifier must >be IODFxx, where xx are hexadecimal characters (0-9, A-F). >To specify more than two qualifiers is optional. The >other level qualifiers can be alphanumeric or national (@, >#, $) characters or hyphen (-). Example: > > 'SYS1.IODF05.WORK' > >If you want to IPL with a production IODF, the production >IODF naming convention must be 'yyyy.IODFxx', where yyyy >is the high level qualifier and xx are hexadecimal >characters." > >Are more than two qualifiers optional, or must the naming convention be >'yyyy.IODFxx'? If I specified <MyHLQ>.IODFxx.&SYSNAME in LOADxx on the new >volume, would I load a 0B1 waitstate for not being able to find ><MyHLQ>.IODFxx? My hope is that the LLQ &SYSNAME is ignored, and the HLQ and >suffix are properly extracted from HSA. My intention is to not compromise >the integrity of Production by using the Sandbox system. Once I can get my >operation datasets off of Sysres, the benefits are obvious :-) > >Thanks for any insight into my unusual(?) inquiry! ---------------------------------------------------------------------- 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
