Depending on you IEFUSI or other functions used to control region size, you may not be getting what you think 0M gives you.
If you try the suggestion of 2000M for region and rerun the job, what do you get? If you have an ACTRT exit in your shop - it may provide the virtual storage map at step end. There you should the Requested/Below/above/ and so forth of storage allocation for the step. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Savor, Thomas (Alpharetta) > Sent: Tuesday, December 12, 2017 11:16 PM > To: [email protected] > Subject: Re: Possible Debug issue > > On this particular test that got all the storage error messages......region > was set to 0M > > Thanks, > > Tom Savor > Software Developer, Sr > FRMS-SCM > Fiserv > Office: 678-375-1307 > Mobile: 404-660-6898 > Fax: 678-375-3280 > www.fiserv.com > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Peter Hunkeler > Sent: Wednesday, December 13, 2017 1:14 AM > To: [email protected] > Subject: AW: Re: Possible Debug issue > > >Debug Tool and Fault Analyzer seem to take a huge amount of memory when > working with COBOL 5. Try setting REGION=2000M. > > > What release of z/OS managed to move the whole common area above the bar? > Seriously, 2000M will probably never be available in the private region. But > if you want to see how much you need to be able to debug, within the maximum > available, specify REGION=0M. > > > -- > Peter Hunkeler > > > > > > -- > Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
