I'm not sure that I follow. The fact that your current application seems to be written in RPG III is not relevant. I'm running a mix of RPG II and ILE RPG (no III). Heck, it your current programs were in Cobol or PL/1 or whatever would make no difference. But that III stuff should have been converted to IV long ago (and then to /free - unless the pgm has a lot of MOVE's, etc.).
Since the new package's underlying database will almost certainly different than what you have now. So the reports you mentioned will probably have to go against a different table(s) with different field names and definitions. Ergo, if that's the case, they will have to be, at least, modified to recognize the new database; perhaps even re-written because of significant differences in data.
Again, I'd trash, I mean, convert that III stuff in any case. Even if you only do it program-by-program as you maintain it. (Sigh, I wish it was that easy to convert II to IV.)
Jerry C. Adams
IBM System i Programmer/Analyst
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Adam West
Sent: Wednesday, August 27, 2008 3:26 PM
Subject: Points to consider when moving from RPGIII to new package
When going to a new package Written in ILE RPG, how much realisitically can you use of your old system. There are many reports and fixes to external data (EDI mostly) that have been developed over the years. Do you consider to migrate anything at all from your old system?
Also, what key changes are there to consider from a applications point of view. That is, what issues that are currently handled by years of hard code do you concern yourself with?
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives