Re: Activation groups for beginners

[Carel Teijgeler <COTeijgeler@xxxxxxxxx>]

--
Buck,

Just a few remarks:
1) I do not think an AG will be removed from a job after ending all PGM's
in the AG with *INLR = *ON. You still have to do a RCLACTGRP.

2) Hopefully we can ban the comparison between AG's and group jobs. Group
jobs have a job number of their own; users can switch between group jobs.
An AG is only a segment of one job.

3) Will this discussion deal with recursive calls? I know using AG *NEW
allows recursive calls. But does the system allow recursive calls to an AG
that is already active. An example:
      Start PGM A in AG QILE
      Calls PGM B in AG ITEM
      Calls PGM C in AG QILE
      Calls PGM D in AG SALES
      Calls PGM B in AG ITEM.
I do not think this is possible. However, I have no experience with this
and do not have the time to experiment at the moment. Perhaps others on the
list have experience with this. It is something that puzzles me for a long
time, but have never read about it.

Regards,
Carel Teijgeler.

>NAG - Named activation group
>DAG - Default activation group
>Scope - How long a variable/program activation/OVRxxx lives
>
>NAGs are not system objects.  They are like QTEMP - there's one for each
>job.  I keep it straight by thinking of a NAG as a subdivision of a job, so
>my QILE runs in my job: 123456/BUCK/QPADEV0001/QILE and your QILE runs in
>your job: 1234567/QPGMR/QPADEV0002/QILE.  They do not know about each other,
>any more than job QPADEV0001 knows about QPADEV0002.
>
>Named AG's come in to play for two things: Shared file opens (override
>scoping) and program activations.
>
>Override scoping.  An override issued in the DAG carries forward into all
>other AGs.  An override issued in a NAG exists only in that NAG for that
>job.  This behaviour is fine for the situation where an OPN CL program does
>some overrides, then calls a mix of ILE and OPM programs, where the ILE
>programs run in a NAG.  If you use shared ODPs, post a to this thread to
>have the behaviour explained in light of AG scoping.  If you want to learn
>about shared ODPs, please open a new thread.
>
>Program activations.  A program in a NAG stays active until the AG is
>destroyed.  This is important if you do RETURN with LR off.  If you use
>RETURN with LR off, post a note to this thread to have this behaviour
>explained in light of AG-based activations.  If you want to learn about
>RETURN with LR off, please start a new thread.
--