Releasing service program resources -- 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.

I'm trying to determine the best way to release service program resources. In most cases, I do not set on *INLR when I return from a service program call.

Closing all the files, setting *INLR on, and RETURNing works. I never thought about not closing the files; it seemed like a good thing at the time, particularly since the compiler stamps its binary feet and issues that petulant "close your files" message if you don't have a CLOSE statement.

I assume I can compile the service program(s) in a specific activation group and reclaim the activation group using the RCLACTGRP command or the CEExxxxx API (I know there's one out there).

Or, I could compile the application program with a specific activation group and the service program with *CALLER (my standard anyway); this would handle it, I think, but chance of somebody compiling something the wrong way is problematic and I'd rather handle it from a design, not execution, standpoint.

The easiest way may be to add a "terminate" subprocedure: it wouldn't need any parameters and all it would do is set *INLR on and return (I think).

Am I missing any options? Is any one of these preferable from a performance/design standpoint?

Thanks,
IRG

_________________________________________________________________ Find high-speed ?net deals ? comparison-shop your local providers here. https://broadband.msn.com

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.