Re: ACTGRP

Buck said:
> > Here's a subtltey: if the program is COMPILED as
> > DFTACTGRP(*YES) it will behave like an OPM
> > program.  If it is compiled as DFTACTGRP(*NO)
> > ACTGRP(*CALLER) and then called by an OPM
> > program it will then run in the DAG but act like an
> > ILE program.  Icky.

Alan replied:

> If the program is full of subprocedures then
> DFTACTGRP(*YES) won't compile.

Right.  That's the point.  OPM programs don't have subprocedures.  An RPG IV
program without subprocedures, compiled as DFTACTGRP(*YES) will behave like
an RPG III program.  That was the whole point of DFTACTGRP(*YES), I guess.

> But why couldn't he change the CL to a CLLE and compile with
> CRTBNDCL DFTACTGRP(*NO) ACTGRP(*NEW), or
> ACTGRP(QILE), and  then ACTGRP(*CALLER) in the RPG?

He could!  It all depends on Lurton's environment.  I think he was
experimenting and ran across this particular oddity: OPNQRYF file opens
don't percolate from the default AG into a named AG, despite the fact that
OVRDBF SHARE(*YES) does.  My comment (above) was only intended to raise
awareness that an RPG IV program can run in the default activation group via
*CALLER as well as DFTACTGRP(*YES).  Sometimes it is difficult to be clear
because many people refer to programs written using RPG IV syntax as 'ILE'.
The RPG IV manual doesn't help that situation.
  --buck