Re: activation groups, compiling CLLE programs

On 09-Jun-2017 14:34 -0600, Gerald Magnuson wrote:

I have noticed that I am doing all kinds of "bad" things in respect
to activation groups...

I don't know where to start, other than maybe changing the command
defaults on CRTBNDCL to DFTACTGRP(*NO) ACTGRP('<our_named_actgrp>')

Using a pre-processor or another form of development build utility might be preferable to just changed defaults. While our_named_actgrp could be considered [significantly] better as a global default than the Default Activation Group (*DFTACTGRP), that still assumes just one preference would be sufficient; without at least, other more robust build controls to customize compiles. BTW, be sure to re-apply any changed defaults, after any OS maintenance is applied, if using Change Command Default (CHGCMDDFT).

we are kinda getting into the habit of compiling our RPGLE programs
as ACTGRP(*CALLER). But since most of our CL and CLLE is set to
*DFTACTGRP, most of our RPGLE is running there as well....

we don't have /copy on our H specs, or any other real helps in
place for this....

what have others done to help with getting programs created with the
correct activation group settings?

Consider using using the CL Declare Processing Options (DCLPRCOPT) in the CLLE source; e.g. to specify the relevant parameters as:
DFTACTGRP(*NO) ACTGRP(named_per_feature)

Additionally, converting CLP to CLLE where reasonable, and in which any required adjustments, such as to Override Scope (OVRSCOPE), can also be effected to reflect that transition from OPM to ILE.