John, >Does anybody know why the RNL cannot be updated immediately when I add a >new GENERIC queue name to it and there already exists some resources >using that queue name? I mean, I can understand it if IBM didn't want to >bother much with coordinating updates between multiple systems. What I >tried to do is add SYSZDSN to the RNL for inclusion.
In my case it's SYSVSAM that we need to specify. On every system there's a vsam data set in use (APPC, if nothing else). And SYSIKJBC/SYSIKJUA that are always allocated in master, even if TSO is taken down. While I can understand the VSAM case, I loath the sysikjbc/ua thing. So that means I need a sysplex IPL. GRSRNL is syntax-tested, and we had two sysplex-wide IPLs since I first attempted the change, but nobody allows the member to be activated when I am not around (and I never am for hardware things). So I keep getting postponed on this one, too. No answer to your original question, just speculation: Once someone has gotten an ENQ a certain way they do not expect behaviour to change. And there are ways to say 'do not mind the RNL settings when you give me the ENQ'. Maybe GRS doesn't keep the original invokers parm around after en ENQ was granted, so there just any safe way to change the RNLs. Regards, Barbara Nitz -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ---------------------------------------------------------------------- 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
