We hit ENQMAXA at 250,000. IBM's recommendation was to double that number. We did, and had no problems. I doubt if you will have any problem with ENQMAXU either.
ESP holds a number of enqueues. At our site I see about 95 for ESPMSTR; 65 for the aux a/s. Those enqueues are long-term, not per event. I wonder how close to ENQMAXU you were before hitting the 80 percent threshold. The number is not externalized anywhere, but the counter is in GRS' virtual storage. Ask IBM support for help finding it, or perhaps our friends on the list can suggest a method. db -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of J Ellis Sent: Wednesday, June 03, 2009 3:04 PM To: [email protected] Subject: ENQMAXU/ENQMAXA We have intermittently began seeing these messages in the log, followed by the 'all clear now' one. *ISG368E THE CONCURRENT UNAUTHORIZED REQUEST COUNT FOR ASID 0122 44 HAS EXCEEDED THE 80 PERCENT THRESHOLD OF THE SYSTEM-WIDE MAXIMUM, 16384 I have spent some time sifting thru enque reports and haven't been able to correlate any Total Events counts to any number even approaching 16K, the address space in the message is the ESP aux a/s and ESP is just coming live in this 2 system plex (running STAR mode). Is there anywhere to look or some D GRS command to be issued at the time of the message to see what qname/rname is being used, OR, short of dumping the A/S to see whats foing on inside of it from a grs view ? ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
