Re: RPG programs as external stored procedures...

Thanks Mark.  I agree, I'm not 100% sure.

So when you say "the named activation group stays out there until the job ends." the job you are referring to is the server job and not the external program from the stored procedure?

Let me try to explain my thinking (which may be flowed)

If a program is called from a menu,  the menu runs in the DAG. But the programs runs in the activation group of the compiled program.

If this is *caller then it would run in the DAG.

If this is *new then a new activation group; is created and is destroyed when the program ends.

If this is named (which until now our shop has never used so my understanding is limited) the system checks if the named activation group exists (in this job/session) and if not the named activation group is created.  Here is where I'm not sure.  So if RCLACTGRP is not specified, then the named activation group exists until the user signs off ending the session and therefore the job.

Is this correct?

Thanks,

Rob



On 2/20/2018 12:08 PM, Mark Murphy wrote:

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.