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

[Joep Beckeringh <joep@xxxxxxxxxxxxxxxxxxx>]

CWilt@xxxxxxxxxxxx wrote:

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

The program stays active until the job ends. You might switch the environment or 
compile a new version, but when you call it you get the original version. The 
biggest problem with the whole situation is that you will probably get away with 
it most of the time. But when something goes wrong you'll have a hell of a time 
finding out what caused it.

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

Obviously when the job ends, but it can also be done with RCLACTGRP.

> 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')?

I would use a named activation group, either QILE or something else. QILE should 
be fine, unless you mix with another application that uses the same setup.

Joep Beckeringh