Why not just use something like LOADPx for the production LOADxx and LOADSx for the sandbox ? Then you can copy your current LOADxx's into those members and coexist. No change necessary to your IODF setup. Otherwise use 2 different IODF HLQ's. You can copy an IODF and maintain the token with no adverse effects (we ship copies of IODF's to multiple sysplexes under different HLQ's all the time -- Token is preserved).
On Wed, 2006-11-29 at 17:01 -0600, Steve Horein 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! -- Jerry Whitteridge Safeway Inc. (925) 951 4184 "MMS <safeway.com>" made the following annotations. ------------------------------------------------------------------------------ Warning: All e-mail sent to this address will be received by the Safeway corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain information proprietary to Safeway and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. ============================================================================== ---------------------------------------------------------------------- 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
