Re: RPG-III to -IV conversion rehash worries

Hmmm.  I thought the numeric overflow was only affected if I converted to
use EVAL.

Correct. The ADD, SUB, MULT, DIV (etc) op-codes work identically in RPGIV to the way they did in RPG III.

Will the date conversion trick bomb if I leave it straight from
the RPG-III style?


No, it'll work just as well (or poorly!) it did in RPG III

I don't think DDEs are an issue.  I'll have to check on *BLANKS and
numerics.

Okay... DDEs are the same in RPG III and RPG IV unless you've specifiedIGNDECERR on the RPG III compile. RPG IV has FIXNBR instead of IGNDECERR,and although they have similar purposes, they don't work identically.

So, decimal data errors (as well as *blanks in a number) aren't an issueunless you were using the IGNDECERR workaround in RPG III.


  If there was a "MOVE *BLANKS   NUMBER" and NUMBER is numeric,

will the -IV compiler catch it?  Or will run-time act any differently than
it did under RPG-III?

Correct me if I'm wrong, but neither RPG III nor RPG IV allows you to moveblanks to a numeric field. You'd have to go through a data structure toget them in there (or read bad data from a file or a parameter, etc).Should work the same in RPG IV as RPG III.

Generally speaking (and thankfully), the legacy apps here were all fairly
well written for their day.  I've yet to come across doing funny stuff with
blanks and numerics, and have never seen a 100.0001 or 10000.01 kind of
multiplication in the code here.  I did come across a FREE opcode in the
converted app but, fortunately, the app being FREE'd was updated at some
point to accept a negative number in a batch number parameter to signal the
program to seton LR and get out.

And that should work, as long as you don't compile the RPG IV version intoa different activation group. Use DFTACTGRP(*YES) if you want your RPG IVprograms to behave like RPG III programs, and you shouldn't have problems.

Naturally, if you want to use some of the modern features of RPG IV,you'll have to change the activation group -- but you can always crossthat bridge when you come to it. Presumably at that point, you'll have aprogrammer who is making changes to the program, and therefore it'll haveto be re-tested, anyway.

Re: RPG-III to -IV conversion rehash worries - Part II