RE: AW: AW: program won't let go of file

[David FOXWELL <David.FOXWELL@xxxxxxxxx>]

> -----Message d'origine-----
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de Scott Klement


> > We have converted a number of OPM that were needed by an 
> application 
> > that runs in a named ACTGRP. Obviously, we have recompiled with 
> > ACTGRP(*CALLER).
>
> I don't understand what you mean.  You say "named ACTGRP", 
> then immediately say "obviously, ACTGRP(*CALLER)".  Huh?  How is this 
> obvious?  Is it a named actgrp, or is it *caller?!   Or is it *CALLER 
> and being called from a named actgrp?

Scott, Eric, thanks.

I meant that as the programs were needed by an application already using a named group, the converted programs were compiled with ACTGRP(*CALLER) so that they would run in said group.



> If your programs are running in OPM compatibility mode, i.e. 
> DFTACTGRP(*YES), then they should behave like OPM programs.
>
> If your programs are compiled with DFTACTGRP(*NO) and ACTGRP(*CALLER) 
> and are called from the default activation group, you won't 
> be able to 
> remove them from memory without ending the job -- but they'll 
> still work 
> fine.
>
> All of these are completely predictable.  None of them are 
> "unpredictable results"

The CLP that called the OPM's use RCLRSC. As the converted OPM's had to be compiled to run in an ACTGRP, I thought that RCLRSC would no longer work in the same manner.