I have this note from a few years ago that consurs:
- Early SAS notes recommended REGION=0M, but with early V9.1, only
for diagnostics AFTER an out of memory condition, a specific REGION
was recommended in http://support.sas.com/kb/18401:
"The thought is that if we have exhausted the full region and
abnormal termination occurs as a result there is not sufficient
ceiling within the address space to properly clean up. This can
lead to damaged libraries, potential hanging and looping within
the address space.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Hunkeler
Sent: Sunday, October 9, 2016 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: AW: Re: CEEDUMP possible following 'new' failure
>Fault Analyzer showed that the last thing that happened in the address
space was trying to load some z/OS routines for termination (if it was not
memory termination then it must have been task termination) and failed to
load those routines because of an out of storage condition.
I have in mind that, at least in earlier times, it was recommended *not* to
code REGION=0M? With REGION=0M the code can to eat up all storage in the
address space. Of course, authorized software may easily overcome any
REGION setting (I guess).
--
Peter Hunkeler
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
