Re: Activation Groups, yesterday and now?

To add additional flavor to Dave's notes...

An ILE pgm that is created with dftactgrp(*no) actgrp(*caller) essentially
tells the ILE pgm to run as an OPM program would... with no boundaries as
the actgrp is adopted from the preceding (calling) pgm.

An example...
If you have CLP pgmA that does an opnqryf, and you create a new ILE rpg
pgmB that is called from pgmA, and you wish to read that opnqryf (though
shameful), the pgmB should be compiled with dftactgrp(*no) actgrp(*caller).

jay

On Mon, Feb 17, 2020 at 5:34 PM <dlclark@xxxxxxxxxxxxxxxx> wrote:

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 02/17/2020
05:09:23 PM:

as far as I understand, activation groups are kind of a shared
memory area for multiple programs to be run in. Correct?

Basically, yes. The default activation group was intended for OPM
programs but is not a good choice for ILE programs. If you specify
DFTACTGRP(*NO) then the activation group becomes QILE, by default. If you
name your own activation group or specify *NEW then that is the activation
group you will get. Basically, activation groups are a performance
benefit (unless you use *NEW) but they can also be used as a boundary for
database commitment control. The enhanced SQL processor also does not run
for the OPM default activation group so ILE SQL programs will also perform
better in the QILE or your own named activation group. I'm sure there is
more but that is all I know off the top of my head.


Sincerely,

Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300

Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331





*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.

*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com