Is your company purchasing a new software package? If so, you basically
have two options:
1. Adopt the company operations to the new package
2. Start modifying the package to fit the company
Unless you are moving to a new version of a package that you are already
using, the likelihood of any of your existing programs working are
virtually nil. Even if you are simply upgrading to a newer version of the
same product, all of those programs need to be reviewed to see if they
need to be modified because of file changes between versions.
Adam West <adamster@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
08/27/2008 03:31 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
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 mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact