RE: actgrp for service program

["Bob Cozzi" <cozzi@xxxxxxxxx>]

You know what... when I said ACTGRP('MYAG') would work with CRTRPGMOD, I was
thinking of the BNDDIR keyword. IBM allows some keywords to pass through the
compilers. Why BNDDIR and not ACTGRP is unclear, except that multiple BNDDIR
can be merged, whereas multiple (and different) ACTGRP would create a
conflict. 

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Buck Calabro
Sent: Wednesday, August 04, 2004 8:56 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: actgrp for service program

> 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



--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.