RE: Overflow in the activation mark counter (Smith, Dave)

There are differences in the activation group parameter on all the various
CRT commands. This can give you unexpected or unwanted results, in my
experience.

Here's how they are on the v5r1 machine upon which work. I don't think
there've been any changes, but could be wrong. Help text tells you what the
original defaults are, and they seem to be right here.

CRTBNDC & CRTBNDCPP have no activation group parameters. I'm not sure where
they end up.

CRTBNDCBL defaults to QILE.

CRTBNDCL has the DFTACTGRP, which defaults to *YES. If you say *NO, the
default for activation group is *STGMDL

CRTBNDRPG has the DFTACTGRP, which defaults to *YES. If you say *NO, the
default for activation group is QILE.

CRTxxxMOD commands do not include it, since activation groups are a
program-related thing.

CRTSQL* have no parameter for activation groups. Hence, you're stuck with
the defaults on the other CRT commands. This is a possible gotcha.

CRTPGM defaults to *NEW, so if you create modules and then link them, you
get the, IMO, undesirable *NEW setting - another gotcha.

At 07:40 AM 3/27/02 -0500, you wrote:
>Tom:  The work volume did not increase.  They do not explain the difference
>at this point.  Their response is:  "I will update you as soon as the
>developer calls and discusses this issue."
>
>Vernon: It looks like the default for "Default activation Group" is *YES
>which causes the program to act like an OPM program.  IBM had us check this
>and in our case, because we are using such a mix of RPG II, III, and IV,
>they reccomend that it should be *YES.