On z/OS 1.8, if that makes any difference. Can anybody tell me the logic at IPL time to force the IPL'ing system into a wait state if the new system's RNL does not match the RNL of the sysplex? Now, I understand why all systems in a sysplex need the same RNL. But I am curious as to why I am not given an option at IPL time to say something like "Oh, I made a mistake, please use the sysplex RNL on this system as well and I'll fix it ASAP." Instead, I get a hard wait on the IPL'ing system.
I messed up yesterday. I thought that I had the RNL's in sync, but made a mistake (changed an RNL member after IPL'ing). This caused a perceived outage on the second, production, system because it "hung up". I guess this was waiting for the DOWN reply on the second system. This caused a "black eye" and more weeping and wailing and gnashing of teeth. Best that I say no more, even from my home account, lest I be smitten. Just another "I hate sysplex" message from me. No, don't bother to justify it. At my shop, it is not justifiable as far as I am concerned (only one box). -- Q: What do theoritical physicits drive beer from? A: An EIN stein. Maranatha! John McKown ---------------------------------------------------------------------- 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
