Re: Help us migrate to ILE RPG

----- Original Message -----
From: "Buck Calabro" <buck.calabro@aptissoftware.com>
To: <RPG400-L@midrange.com>
Sent: Wednesday, January 17, 2001 12:12 AM
Subject: RE: Help us migrate to ILE RPG


> Gerald Magnuson wrote:
>
> >We are a small shop (3 programmers, 1 manager).
> >We need to convince management on cost benefits of
> >migrating to ILE.  (time justification is what they
> >want the most)
>
> I don't recall exactly, but here's what I *think* I did and how long it
took
> me:
> 1) Convert a familiar RPG/400 program to RPG IV:
> CVTRPGSRC (comes with the compiler) logfile(*NONE)
> WRKMBRPDM, edit and compile ACTGRP('QILE')
> Time: 10 minutes.
>
> 2) Add code using new syntax:
> WRKMBRPDM, edit.  Use D specs to define a new standalone field with a REAL
> variable name like CustARAmt, add a few lines of code to use the new op
> code; eval CustArAmt = CustArAmt + CUR + OVR30 + OVR60 + OVR90.  Compile
> ACTGRP('QILE')
> Time: 15 minutes.  You can use the converted D specs as a template.
>
> 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.

<snip>

Buck,

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 ...).

Joep Beckeringh



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