Re: actgrp for service program

A module ACTGRP would have to be understood to be a preference and yes, this
would cause some confusion as to when it's used or ignored.

In the case of your program example, only the entry module (*ENTMOD) would
be used for determining the ACTGRP and the other module's ACTGRP parm would
be ignored.

In your service program example, *ENTMOD would be irrelevant because there
is no entry modules for a service program.

OK, so maybe this is a bad idea.


> There are a few issues with that concept.  How would one do CRTPGM on
> MODULE(MOD_A MOD_B) if each module had a separate activation group
> specified?  How would one include a single hard-AG module into
> separate service programs if one wanted each service program to run in
> a different AG?