Migrating OneWorld off iSeries.

rolimn

Member
I am looking for anyone who may have a table of issues to analyze while evaluating migration of OneWorld from iSeries to a different platform / database. Customer history is that it uses JD Edwards since WorldSoftware so I'm afraid there may be too much dependency on the platform like RPG programs off OneWorld updating OneWorld tables, table triggers on the object level which will not be automatically taken to a different database.... What else should I be concerned with?
 
Nelson,

What platform would you like to migrate to and why?

Triggers are used on coexistent installation (World +
OneWorld) within some tables to reflect updates on
a consistent and understandable way for both products.

Once you crossed the bridge to your new platform, you
should no longer need these DB2/400 triggers.

However, if your customer uses custom in-house RPG
programs to interface with 3rd party apps on the AS/400,
you'll have to think how to deal with that data on the
new platform.

Finally, most of the issues depend on what platform you
are migrating to. Win-SQL, Win-Oracle and Unix-Oracle
have all different "tips and tricks" for a successful
migration.

Boa sorte! (Good luck)

Sebastian Sajaroff
 
Back
Top