IBM got back to me quickly on this one. Searched back in the SYSLOG, and found a $HASP183 message giving the actual request which went over the limit. $HASP050 reports that the limit was exceeded during the interval, but does not give the size of the "exceeding". So add some external buffers and try again.
John Mattson/Epson 09/08/2009 11:13 AM Expire Date: 09/03/2011 To IBM Mainframe Discussion List <[email protected]> cc Subject $HASP050 JES2 RESOURCE SHORTAGE OF BUFX - 0% UTILIZATION REACHED This reminds me of my bank (USAA) which I cannot get to stop sending me reminders that my credit card payment of $0.00 is due. I am not quite sure WHY JES2, zOS 1.08, puts out this message, and sends the sysout to the bit bucket... but I would like to STOP it. Could it be that the need for BUFX is really greated than 79, but the message just does not reflect the truth? $HASP050 JES2 RESOURCE SHORTAGE OF BUFX - 0% UTILIZATION REACHED A TOTAL OF 79 BUFX ARE CURRENTLY DEFINED, OF WHICH: 0 (0%) ARE IN USE 0 (0%) ARE BEING WAITED FOR 1 PROCESSORS REQUESTED BUFX BUT DID NOT WAIT THE LARGEST UNFULFILLED REQUEST WAS FOR 1 BUFX A MINIMUM OF 1 BUFX IS REQUIRED TO SATISFY CURRENT DEMAND ---------------------------------------------------------------------- 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
