I'm not sure what you mean by maintain production integrity, but if it is to totally separate datasets for your production and sandbox LPARs that sounds right. If that is what want to accomplish I would start by asking why do you need separate SYSx.IPLPARMs and IODFs? Is this a management mandate or an audit requirement or just the way it has always been done? I have a mirrored volume that has my SYS0.IPLPARM and my production IODFs. I rely on the mirroring to provide the hardware integrity and so far have not had any problems. I have multiple LOADxx members for my two systems (prod and system programmer sandbox) in SYS0.IPLPARM. The IODFs are cataloged in shared user catalog which facilitates access on both systems. This setup has been working for me for about 10-12 years without any issues. I don't know if this accomplishes what you need or not or if it is an option for you, but it is fairly simple (you know the KISS theory) works for me.
Regards, Bill -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Horein, Steve (HAR-ORL) Sent: Thursday, November 30, 2006 4:40 PM To: [email protected] Subject: Re: Moving LOADxx Well <expletive deleted>! So basically I'm not in a very good position, and back to square one. It seems to me that to accomplish what I want, and maintain Production integrity, I need to create an uncataloged copy of <MyHLQ>.IODFxx (which is found in HSA) on a new volume. I then create SYSx.IPLPARM on this new IODF volume, utilizing LPARNAME filtering, PARMLIB concatenation, all the 'new' bells and whistles, etc, in LOADxx (or more likely LOADxy). I change my LOAD parms to point to new IODF vol and LOAD member, IPL and off I go! Does this sound feasible? Thanks, Steve Horein ---------------------------------------------------------------------- ---------------------------------------------------------------------- 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
