Re: DFTACTGRP(*NO) ACTGRP(*CALLER) was RE: More ILE 101

[Scott Klement <klemscot@xxxxxxxxxxxx>]

> Resources not being deallocated has been mentioned.  But are we just looking
> at memory not being freed until the job is ended?  Files are still closed
> correct?  I also thought RCLRSC had no effect, but Scott mentions that it
> will cause variables to be re-initialized even if *INLR was *OFF.  Is there
> any other effects?

File open/closes are an aspect of the RPG cycle.  If you end with
*INLR=*ON they're closed.  If *INLR=*OFF, they're not closed, but RCLRSC
will close them.

Really, it works the same way as an OPM program with one slight
difference -- the program isn't deactivated, memory isn't deallocated,
just reinitialized.   This will result in faster access on subsequent
calls at the expense of memory.


> When are resources deallocated when using a named activation group?

When you reclaim it.  If you never reclaim it, it behaves the same way as
the *CALLER running in DAG.


> Biggest question...what do I use in place of DFTACTGRP(*NO) ACTGRP(*CALLER)
> when most of my ILE programs are called from and may call OPM programs???
>
> Should I use *NEW unless the program is called repeatedly?
> Should I have all ILE simply use a single named activation group ('QILE')?

If your ILE program was OPM, would you end with *INLR=*ON or *INLR=*OFF?
If it's *OFF, you probably want to use "named."  IF it's *ON, you may want
to use *NEW instead so that resources are automatically reclaimed.

I don't like to use QILE because I'm always paranoid that some 3rd party
software will leave something running in QILE that it assumes won't ever
be reclaimed.   For that reason, when I'm not using *NEW, I name the
actgrp after the program that created it.  This way, there's no conflicts
if I reclaim it.

But, I must say, calling ILE from OPM has been rather rare for me.  I've
been using ILE for 8+ years now, and I don't think I've called ILE from
OPM more than 20-30 times.   Usually, a given menu option is all-ILE or
all-OPM.