Re: actgrp for service program

["Joe Lee" <LeeJD@xxxxxx>]

How about an enhancement that would allow you have the equivalent of H
specs (such as BNDDIR, ACTGRP, etc) in the binder language? Since that
is sort of the equivalent to a source member for a service program. I
would love to be able to use 14 on the binder language and have the
service program created instead of having to run CRTSRVPGM and having to
look up the correct parameters for that service program. Especially when
it has been a while since I last modified it, or if it is a service
program that I have never worked on before. 

Joe Lee

>>> buck.calabro@xxxxxxxxxxxx 08/04/2004 06:56:06 >>>
> It would seem that _IF_ an ACTGRP could
> be specified at module creation, then a
> CRTPGM ACTGRP(*ENTMOD)
> _COULD_ use this value rather than
> the new defaults (QILE or *NEW).

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?

I think the typical answer to creating service programs (or even *PGMs
with multiple modules) is to use some variant of MAKE.  That is, any
time one uses PDM 15 followed by CRTPGM or CRTSRVPGM, one should
probably use an automated tool to properly bind the modules and set
the activation group attribute.  A CL program would be good enough.
  --buck