RE: QILE activation group?

James,

There's some vagueness in the ILE spec that I'd like to have others comment on that's brought up by your post below.

Program A, running in system-assigned activation group 32 calls program B for the first time and program B was compiled CRTPGM ACTGRP(*NEW), the system will create a new activation group in your job and call it, say, 33 and run program B in that activation group. This much is clear from the spec.

If program B returns without setting on LR and program A or another program operating in activation group 32 calls program B again, the system will continue to use the copy of program B in activation group 33. This is NOT clear in the ILE programmers guide, but I believe it to be the case. If program B sets on LR before returning to program A, will the system clear the activation group? That isn't clear either, though it is implied in some statements about system-defined activation groups along with explicit statements that the system will NEVER clear user-named activation groups (like QILE) without an explicit RCLACTGRP. If the system does clear activation group 33 in that case, it must create another new activation group when Program B is called again. Even if program B was running in a named activation group that was not cleared, one would expect files to be closed and variables to be cleared if program B returned after setting LR.

I'm sure Jon, Susan, Paul, et all, have instructed me how this works. But I'm getting old and don't remember for sure and went to the ILE programmer's guide to confirm and couldn't find a definitive answer.

DK

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, July 29, 2013 12:56 PM
To: Midrange Systems Technical Discussion
Subject: QILE activation group?

When did the default for compiling with DFTACTGRP(*NO) become "QILE"?
I'd have to bring up the V4 box to be sure, but as I recall, the default
for DFTACTGRP(*NO) there (V4R4 with V4R2 development tools) is "*NEW."
And I even recall having to explicitly play with activation groups, to
make something work properly on one customer installation.

I was expecting to have to come up with my own named activation group,
to keep a DFTACTGRP(*NO) RPGLE program from reinitializing itself every
time it's called.

--
JHHL