Re: OPM called by program running in a named activation group

On 24/03/2009, at 11:25 PM, David FOXWELL wrote:

I have an interactive program A running in DFTACTGRP at the start.

There's the start of your problem.

Depending on a choice of client type by the user, pgm B gets called in the named ACTGRP for that type of client. Pgm B does nothing but call pgm C so it is activated in the same group (ACTGRP *CALLER).

Since ACTGRP is an attribute of the compiled program and cannot be changed PGMB isn't really a single program but rather you have multiple programs compiled from the same source each compiled with a different name and specifying a different activation group. Yes?

So you bounce from *DFTACTGRP, to named ACTGRP, to *DFTACTGRP, to who knows where else? What a mess. Like I said earlier: bad design.

Why do you want/think you need a separate ACTGRP for each client?

I was worrying about pgm C calling anything outside it's ACTGRP.

In this case that is a legitimate concern but only because the design is so messed up. This sort of problem is entirely of your own making and can be fixed by correcting your use of activation groups.

Least intrusive fix would be to make PGMA run in a *NEW activation group then convert the RPGIII to RPG IV and run in *CALLER.

Proper fix is probably to revisit the use of separate activation groups for each client.

Give people a sharp tool and they'll just cut their fingers off.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------