Re: RPG III (RPG/400)

While I agree with "best practices", if we are held to that standard here,
almost none of these old RPG programs will ever be converted, per the
reasons shared in my previous post.

I can't count the number of times I've tracked
back a production issue to a small change
made in some other portion of an app.

This seems to imply that the "issue" already existed in the old, RPG-III
code. It's not that I don't care that it's there, but the converted
program won't behave any worse than the original.

- Dan

On Mon, Nov 2, 2015 at 3:22 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

My .02...

Best practice would be to regression test the app's functionality
regardless of rather or not you've changed one line or 1,000.

I can't count the number of times I've tracked back a production issue to a
small change made in some other portion of an app.

And yes, sometimes I was the guilty party. :)

That being said, CVTRPGSRC is as bullet proof as you'll ever find.

In 10+ years, I've only had 1 "working" RPG III program that failed after
conversion to RPG IV. I say working because the issue was by a parameter
mismatch. It just happened that the RPG III didn't get the same crap in
memory the the RPG IV version did.

Charles