Re: Automated cleanup

["David Morris" <dmorris@xxxxxxxxxxxxx>]

One more thought,

What about using a scope message?   Even though a control boundary is not 
viable, the program level would probably be OK.  If I send a scope message from 
a sub-procedure bound into a service program when is the scope program called?  
The manual is very vague.  It simply says the program is called when your call 
stack entry, program, or job ends.  It then goes on to talk about the only 
difference between call stack entry and program is when a transfer control 
occurs.  This is further confused when later it says "when the caller's program 
ends", implying they are different.   If anyone has any experience in this area 
I would appreciate a summary.

Thanks,

David Morris

>>> "David Morris" <dmorris@plumcreek.com> 09/09 10:17 AM >>>
RPG Fans,

I am working on a cleanup process that performs housekeeping functions for 
called procedures.  This is used in cases where a called procedure allocates 
memory, creates temporary objects, etc. and the caller controls the processing. 
 In most cases we don't want to reclaim the entire activation group.  Is there 
a way to trigger a procedure to be called on a normal return?  At this point we 
have an explicit call.  The procedure registered by CEERTX is only called if 
returns without a return.  If we can't cause a procedure to be called on all 
returns we will probably add a trace facility that logs allocations and 
deallocations.  One current idea is to produce the trace using messages when in 
debug (similar to SQL or query).  Anyone have any ideas?

Thanks,

David Morris


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *