>I got a question from one of my co workers on why his job abended with an >S822 Reason=00000014 > >The job have over 200 steps running mostly DB2 Tools from CA. There is no >region size on the jobcard. Each step (except the one that got the S822) >has a REGION=0M > >Our default region size is problem 1M.
>I am thinking with the changes to IEFBR14 for z/OS V1.11 (we are coming off >z/OS V1.9) that we just need to add a region size to this step. Whatever the reason for the 822 is (new release/changes to IEFBR14 - though I doubt that): With a region size of less than 16MB (? - in any case less than your private region below) MVS DOES check region sizes below the line. Something maybe in the prior steps hasn't properly cleaned up - and I *would* investigate that if I were you - so 1MB region below isn't left (assuming your IEFUSI does not override that 1MB region size to something larger). With a region size of 0M MVS does NOT check region below the line for size. That's why your region=0M steps do not show any problem, even though probably a lot less private below is available than you think it is. I spent quite some time debugging a similar 822 on certain Endeavor-jobs. My IEFUSI unconditionally overrides any region smaller than 32M to give the full region below. Since only about 7.5MB instead of the full 8MB region were left and the rest not properly freed by Endeavor, that job kept abending 822. Setting region=0M cured it, and IBM told me that with region sizes larger than a certain size (16Mb or 32MB) VSM does not check region size below anymore. Regards, Barbara ---------------------------------------------------------------------- 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
