RE: Help us migrate to ILE RPG

Buck wrote:
> 3) Add a subprocedure:
> Scan the Midrange Archives for examples of subprocedures.  Look at the
> Redbook "Who Knew You Could Do That..." for examples.  Edit code, compile,
> test.
> Time: 1 hour.
>
> Time expended: call it 4 hours in case I missed some stuff.  
> There's no ILE here; just RPG IV.

Joep added:
>This is not true, there is ILE here.  As soon as you compile with
>DFTACTGRP(*NO) you are creating a 'real' ILE program.  If you want to use
>RPG IV in an OPM environment, you'd better stick to DFTACTGRP(*YES).  
>Sadly, this means no subprocedures.  Of course there is nothing 
>wrong with building real ILE programs, but mixing those with OPM 
>programs can be tricky (e.g. OVRDBF + OPNQRYF in OPM CL, 
>then calling an ILE RPG program ...).

Thanks Joep - I knew there was something I missed!  You are absolutely right
that you need to use a named activation group to use subprocedures.  Your
warning about the overrides is right on as well.  Here, when I need to mix
OPM and ILE (that is, an RPG IV program with a subprocedure - no binding) I
either change the OPM CL to OVRxxx OVRSCOPE(*JOB) or compile all the
programs including the CL as ILE.  Typically, here each CL program calls a
very few RPG programs, so there's not much to change.

I tend to think of ILE as binding and activation group management.  In our
business, we use only one named AG - QILE, so there's no "management" aside
from the OVRxxx issue.

Good catch, and thanks!

Buck Calabro
Aptis; Albany, NY
"Nothing is so firmly believed as
 that which we least know" -- Michel Montaigne
Visit the Midrange archives at http://www.midrange.com
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---