RE: Activation groups for beginners

["David Morris" <David.Morris@xxxxxxxxxxxxx>]

Phil,

The ability to change an activation group for a program is OK, but
ideally you would be able to specify the activation group for a
program with the activate program APIs.  You can simulate this
in most cases using a stub program with dummy parameters, but
the activate program API would be ideal.

Here is one for your activation group faq. Have you ever noticed
that a *caller program called from a command line will run in the
previous non-default activation group on the stack? I don't know
why that works, it is unlike other activation group handling on the
system, but it is nice that it does.

David Morris

>>> sublime78ska@yahoo.com 03/18/02 04:15PM >>>
Buck,

> One of the things I find annoying about the AG concept is that the AG
is a
> property of the program/service program rather than a job property.
That
> is, I can't set AG names on the fly - I need to compile my
> program.  I can't
> even do a CHGPGM to set the AG - it must be a re-compile.  I
> guess that's my
> hint that I should plan my AG strategy carefully, eh?

Well, actually you can change the activation group with the UPDPGM
command:

UPDPGM PGM(PHILLIB/PRMORG01) MODULE(*NONE) ACTGRP(PHILAG)

It creates a new program - the old one is moved to QRPLOBJ.

If you call the pgm, don't reclaim the ag, change the ag with UPDPGM,
then
call it again, both ag's will show in option 18 of wrkjob.

>
> How would making AG05 *NEW change things?
>

Can't change the ACTGRP with the UPDPGM command if the activation group
is
*NEW.

Phil