> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Eatherly, John D [EQ] > Sent: Thursday, April 03, 2008 9:43 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Re: Another RNL question > > > We have a parmlib that is shared by the whole sysplex. And > the GRSRNL is one of the members that is in that library. > That way, they are always the same. You don't have to > duplicate members. > > Thanks > John Eatherly
The same problem can still hit you, if you mess up the way that I did. By updating the share GRSRNLnn member, then IPL'ing a system. Yes, I've learned the hard what "DON'T DO THAT!" I plan to declare the GRSRNLnn members to be WORM members. They will NEVER be changed once they are used for an IPL. Instead, I will change the IEASYSnn member to point to a new GRSRNLnn member that has never been used before. But the question remains as to why I cannot more easily recover from this sort of user error? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
