Patrick O'Keefe wrote:
You metioned defects and memory leaks. In my world, that
answers your question. As far as I'm concerned, an abend is
easier to deal with than a run-away storage allocation routine.
Making this into a discussion of abend vs runaway storage allocation is
really a non sequitur. Setting a specific storage limit is really the
same as not setting a specific storage limit. There is a limit either
way. Only one is usually lower than the other and will be reached sooner.
The question of whether an abend is produced, when the limit is reached,
depends upon whether the first-to-fail storage allocation service call
is conditional or unconditional. These days, I like unconditional calls
because I prefer an abend to terminating after issuing a message like "i
can't get storage".
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
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
