I've learned to update the one used at IPL time. Then make the change dynamically specifying that member to be used. That way things "SHOULD" be the same upon the next IPL of one of the systems.
The biggest problem I run into are enqueues that will not release, thus holding up the dynamic RNL change. Depending on how badly the new RNL is wanted, eventually we end up with a plex-wide shutdown and restart in this instance. Although I will try again several times, trying to pick a point where the "hanging" enqueue may be gone. Your method is still perilous. Since I make the change dynamically first, I feel good things will be fine at the next IPL. In your case, you probably could have made a dynamic change on the running system to the RNL definition the other system pointed to, then RE-IPL the down system. This is all part of the learning process for sysplex. Once things stabilize, you will wonder how you ever got along without it. <vbg> On Thu, 3 Apr 2008 14:31:34 -0500, McKown, John <[EMAIL PROTECTED]> wrote: >> -----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? > >-- ---------------------------------------------------------------------- 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
