Re: When does manually allocated memory get released? -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi, Vern:

OAR handlers are certainly a "special case" that should definitely take care of allocating and freeing their own storage, and not just allocate a bunch of stuff and "leave it up to the system" to clean it up. Because, who knows how long a using application (that calls the handler indirectly , via the F-spec) may be running? It might be a "never ending program"... :-o

Mark

> On 10/8/2010 12:22 PM, Vern Hamberg wrote:

Mark

I guess I'm of the school that says not to depend on hidden processes to
clean up things. And I'm not sure about using some hidden thing
sometimes, not in other situations.

In the handler I'm working on, I would not want to end the activation
group, since I'm not the one who started it. I'm using *CALLER in the
*SRVPGM that is the handler, as I recall.

I also don't know how many reads or other operations will be done
between open and close. So I want to explicitly dealloc a particular
based DS (that keeps the state between calls) in the event of an error
and when closing the "file".

Just my way today!

Vern

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.