Re: OPM *INLR and ILE actGrp

Well before you try and explain RPG in COBOL terms make sure that _they_
understand what they are currently doing. I've worked with hundreds of
COBOL shops on S/36, S/38 and IBM i and I doubt more than 10 to 20% had
_anybody_ on board who really understood.

Also understand that the effect of these COBOL options is different in ILE
COBOL to OPM COBOL for reasons that I won't go into.


Jon P.

On Aug 15, 2024, at 1:46 PM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>

wrote:

I really wish I could Jon - REALLY... but guess what?

This is a 100% cobol shop. :)

Hey, I told them I was an RPG guy when I came on board. :)

so using RPG but need to relate back to their COBOL references some how.

Jay




On Thu, Aug 15, 2024 at 1:38 PM Jon Paris <jon.paris@xxxxxxxxxxxxxx>

wrote:

I would leave COBOL out of the comparison completely.

Two reasons - first STOP RUN/EXIT PROGRAM/GOBACK all have implications
that really don't map to RPG

Second (and more importantly) in my experience working on the COBOL
compilers, the vast majority of COBOL programmers have no real idea of

what

the differences are. Not to mention that there are subtle differences
between mainframe COBOL, IBM i COBOL and other dialects.


Jon P.

On Aug 15, 2024, at 12:52 PM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx>

wrote:

appreciate all the feedback.

I'm aware actgrp's do much more...

I'm trying to put together some presentation material for a more jr.
audience and I think comparing actgrps to inlr could be helpful.

Also from my understanding INLR (rpg) is very much like STOP (in cobol)
right?
but yes, ACTGRP spans all ILE languages and has a universal behavior

thanks for all the things to consider

Jay

On Thu, Aug 15, 2024 at 12:18 PM Scott Klement <

rpg400-l@xxxxxxxxxxxxxxxx>

wrote:

Jay,

Essentially, setting on LR in OPM destroys the current program
activation. Destroying an activation group, similarly, destroys a
program activation. So in that respect they are the same.

But:

Activation groups can be a GROUP of activated objects (programs and
service programs) rather than just one, so you can clean up "all your
junk" at once.

Activation groups can have memory allocations, commitment scopes, and
file overrides scoped to them.

Activation groups apply to all ILE languages (whereas LR only exists

in

RPG.)

Activation groups support teraspace storage and (potentially)
multi-threaded access.


I could go on... so yes, there are some similarities, and that's a

handy

way to think of things. But activation groups can do far, far more.

On 8/15/24 10:43 AM, Jay Vaughn 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.

--
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.

--
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.

--
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.

--
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.