Hi Mark, There are other places (e.g. JES exits) that can affect region sizes. I assume that you've checked obvious things:
> REGION=0M is specified on the JOB (i.e. to override any default) and no other > REGION= parameter (e.g. on EXEC statements) is specified. > The subpool associated with the failing request (should be displayed in the > message and/or dump) is in the private area and RES=31 or RES=ANY I don't mean to be insultingly rudimentary; I often overlook things that stare me in the face. Cheers, Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Pace Sent: Tuesday, March 22, 2011 12:37 PM To: [email protected] Subject: Region size I have an SE that has job running out of memory. The error message says that he ran out of storage at 1792MB. We have do not have an IEFUSI exit, and we are using the default IBM IEALIMIT. So with REGION=0M he should be getting everything possible. So as I understand it my only ability to give him more storage would be to shrink CSA/ECSA and SQA/ESQA. What I can't find is how to determine what are correct sizes for my environment. I don't want to just willy nilly reduce the sizes of these parameters and then have my system puke. What is the correct way to monitor and adjust these parameters? -- Mark D Pace Senior Systems Engineer Mainline Information Systems ---------------------------------------------------------------------- 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
