Re: OPM *INLR and ILE actGrp

Kinda.

First of all INLR = *On in an ILE program will effectively behave the same way as in OPM. Under the covers it is different but from the programmer's perspective, it behaves the same way.

One big difference is that destroying an AG effectively sets on LR for ALL the programs running in that AG.

There are many other differences, so rather than try to draw comparisons I would suggest you just learn more about AGs. If you want to avoid pitfalls this is a good place to start. https://authory.com/JonParisAndSusanGantner/The-Seven-Deadly-Sins-of-ILE


Jon P.

On Aug 15, 2024, at 11:43 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

Would anyone agree or disagree that *INLR is very much like actGrp's?

Instead of turning *INLR on or off to manage persistent memory storage and
files opened, actGrp's pretty much do the same thing.

What are any real big differences between the two?

in a call stack...

OPM - pgm1 (inlr=on), pgm2 (inlr=off), pgm3 (inlr=off), pgm4 (inlr=on)
really isnt any different than...
ILE - pgm 1 actgrp(*new), pgm2 actgrp('named'), pgm3 ( 'named'), pgm4
actgrp(*new)

for the opm, on the next call, the pgms with inlr=off will still have their
files/memory still resident, and the others will not
for the ile, on the next call, the pgms with actgrp('named') will still
have their files/memory still resident, and the others will not.

yes? no?

thanks

Jay
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.