Migration Guide


Using the migration tool

When you load Version 3.0 applications into a Version 5.5 image, warning messages such as "Defined global <name> in unmanaged namespace" might print to the System Transcript window. These messages indicate that you need to change your code so it runs cleanly on Version 5.5. The base migration tool can help you fix the code.

Tip icon
If you cannot load your applications because class names are different for Version 5.5 or because parts used in the Version 3.0 application are now obsolete, see Obsolete code. If you are migrating database applications, see Migrating database applications.

If you can load your applications, but they use any of the classes listed in Obsolete VisualAge code, load the configuration map VisualAge, Obsolete Parts, and then run the base migration tool.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]