Re: RPG 7.1 CONST problem ** RESOLVED **

And it's not deactivated when the CALLING program ends with *INLR on, either, right? It's only deactivated
when its activation group ends. So what we're saying is that the procedure in the incorrectly created DFTACTGRP(*YES) program will be subject to deactivation when the program sets on *INLR, while a procedure in a DFTACTGRP(*NO) will either be subject to deactivation only when the activation group ends, or _never_ in the case where the program is *CALLER and called by a DFTACTGRP(*YES) program (well, not until the entire job ends, anyway).

So the difference is that in this incorrectly created program a procedure will have been deactivated (whatever that might entail) within an activation group that is not deactivated (that is, the default activation group), and that this creates an exposure of some kind. I got it, I think.

Joe

Joe,

A program compiled with DFTACTGRP(*NO) is not deactivated when it ends
with *INLR=*ON. Not even if it's ACTGRP(*CALLER) and in the dftactgrp.


On 2/24/2011 11:46 AM, Joe Pluta wrote:

Now instead that same program calls a program with DFTACTGRP(*CALLER)
which has bound procedures. When the calling program ends with LR and
gets deactivated, would not the same caveats apply? Or is it different
because the procedure is actually part of the program that is deactivated?