Re: RPG programs as external stored procedures... -- 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.

On Sun, Feb 18, 2018 at 6:38 PM, Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:

So if *new or a named activation group is specified for the external

program, each time it processes a stored procedure it will create and
destroy the activation group. So my understanding would be that if all
programs called by the external program specified *caller and the external
program didn't call itself then there wouldn't be any difference (under the
previous circumstances) between *new and named activation groups. In both
cases when the external program starts an activation group is created and
when the external program ends the activation group is destroyed.

So our existing strategy of the initial program using *new should be
acceptable.

I think you are confused on the named activation group. Only a *NEW
activation group is automatically destroyed when a program ends. The named
activation group stays active on program end, and is only created when
necessary. You can manually end a named activation group with RCLACTGRP.
Otherwise, the named activation group stays out there until the job ends.

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.