Re: DFTACTGRP(*NO) ACTGRP(*NEW)

Buck Calabro wrote:
> 
> The hitch in the gitalong comes when I decide to use my first subprocedure.
> I'm forced to choose an activation group then, because the compiler insists
> on running outside the DAG.  I can cheat and use *CALLER, but that puts me
> back in the DAG, where the compiler didn't want me.  There must be a good
> reason for that...
> 

Buck, the compiler only doesn't want you to have a DFTACTGRP(*YES)
program calling procedures.  There is a good reason for that (some very
low-level system reason that I don't really understood ...), but it
doesn't apply to *CALLER programs that end up in the DAG.

The only real problem I'm aware of with ILE running in the DAG is with
*SRVPGMs that do I/O and leave files open across calls.  When a RCLRSC
is done, bad things happen.  (Even where RCLRSC is "never" done, it is
sometimes done.)