RE: Activation groups for beginners

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

See below,

Scott Mildenberger

> -----Original Message-----
> From: Smith, Nelson [mailto:NSmith@lincare.com]
> Sent: Wednesday, March 06, 2002 6:36 AM
> To: 'rpg400-l@midrange.com'
> Subject: RE: Activation groups for beginners
>
>
> >
> This is where I have had problems trying to use *CALLER on my service
> programs.  When called by an OPM, I sometimes get
> unpredictible results.  As
> much as we all would like to see one simple solution to be
> used throughout
> our shop, nothing seems to fit every situation. For this
> reason, I have
> wound up with:
>
> - *NEW for known, definite driver ILE programs.  Usually,
> menus and CL's.
> (with the caveat that they aren't called repeatedly)
> - *CALLER for programs definitely known to be called ONLY by
> those driver
> programs.
> - A specific NAME for small, tightly integrated, standalone systems.
> - The name "TRIGGERS" for trigger programs.
> - The name "SRVPGMS" for service programs (generic service
> programs, that
> is, not those tightly integrated in to a standalone - system).
> - The name "QILE" as a catch-all for everything else,
> especially where I'm
> not sure at design time who will be calling the program.
>
> This system has been in use for about four years and seems to
> provide nice
> boundaries between sections of a job.  It's also quite
> helpful when looking
> at the program stack.
>

The only point I would make here is that you have to be very careful if you
want any overrides to affect your trigger or service programs.  The
overrides cannot take the default which is to scope to the activation group.