Yes, I know I really need to complain officially with IBM on this one. 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. Of course, since I do have UNIX filesystems mounted, this resulted in a "in use" scenario. Now, I understand that if two systems had incompatable ENQs active that would be a problem. But, in my case, I only have a single system running in the GRSplex at present. So, basically, nothing much (I guess) really needs to be done. But even if I had multiple systems active in the GRSplex, it seems that the systems could "talk" to each other and determine if there were any conflicts before complaining (in effect) to me that the change has been delayed due to the resource being actively used. If there were no conflicts, then just do the update.
-- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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
