You can't enforce ACTGRP(MYCOMPANY) via standard h-spec for a service
program...
ACTGRP on an h-spec is only applicable to *PGM objects and only when you
use CRTBNDRPG.
The default for CRTSRVPGM is ACTGRP(*CALLER)....now I won't say IBM's
defaults are always perfect, but I think that one is. :)
IMO, the decision to run a service program in a named activation group
instead of *CALLER is one that requires a through understanding of ILE and
activation groups...
Commitment control and/or overrides is the most likely place for trouble
when don't use *CALLER for service programs.
Charles
On Wed, Feb 6, 2013 at 5:27 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
If the rule (enforced by the standard H-spec) is ACTGRP(MYCOMPANY) how
would this happen? Nevertheless, my real reason for replying is to try
to work out what 'now you have trouble' might mean. How many people use
STATIC in such a way that the static variable MUST NOT be segregated by
AG? If that's the case, then they're beyond being a beginner, and
certainly don't need a simple (and simplistic!) ILE check list.
Is it really so hard to remember 2 rules...
*PGM ACTGRP(MYCOMPANY)
*SRVPGM ACTGRP(*CALLER)
Instead of the one?
Nope! I myself have quite a few *CALLER service programs with a single
named AG for the calling programs. What I wanted to do is dispel the
pernicious notion that getting started in ILE is complex and error
prone. Trying to distil the simplest approach, if you'll allow me the
vanity. I'm enjoying the discussion very much; thank you!
