Migration from a previous version of EGL

The migration process from a previous version of EGL depends on the version that you are migrating from. Parts of the process are automated and other parts involve manual changes.

You do not need to run a migration tool to move from version 8.0 to a later version.

You also do not need to run a migration tool to move from version 7 to version 8.5. However, in this case, be aware of the considerations in Migrating from version 7.0 and after.

To migrate from a version earlier than 7.0, you must migrate your code from one level to the next until you reach the version 7.0 level.

You can use the following migration tools:
V6.0 Migration
The V6.0 migration tool converts EGL source from versions V5.1.2 and V6.0 to comply with EGL V6.0 iFix001.
V7.0 Migration
The V7.0 migration tool migrates code from EGL version 6.0.1 and later to the current version.
Workspace Migration
The workspace migration wizard migrates projects from version 6.0.x or 7.0.x to the current version. It runs automatically when an earlier project is detected. You can select to run the migration later. If you use web projects in version 6, you must migrate your workspace to version 7 before trying to use those projects in version 8. Version 8 cannot migrate version 6 web projects.

Before you begin

  • If you are migrating web projects from version 6, migrate your workspace to version 7 before you install version 8.
  • Bring your runtime environment, in which you generate Java™ or COBOL from EGL, to the correct level for EGL version 8. To update your environment, you might need to install APARs, PTFs, or both.
  • Before you import projects into your new workspace, set your preferences. For example, if you use the VisualAge® Generator compatibility preference, set that preference before you import the files to convert.
  • Import all projects that are referenced by the project that you are migrating into your workspace. The migration tool attempts to resolve references to parts in the migrated code. You do not have to migrate the referenced projects at the same time, but they must be present for the tool to work.
  • All Eclipse web projects, not just EGL web projects, are updated automatically to work in the new version of the workbench. This statement does not mean that your EGL code is migrated automatically; it means that your web projects are updated to the current standard.

    To determine whether your web projects are being updated, watch for the Project Migration window when you open and build a web project from a previous version in the V7.0 workspace. If you do not have automatic builds enabled, manually build the project by clicking the project and then clicking Project > Build Project.

  • Determine the current version level of your code. Depending on your current version, the steps for migration differ. Migration paths are available for code at these levels:
    • Version 5.1.2, up to but not including version 6.0 with interim fix 001
    • Version 6.0 with interim fix 001, up to but not including version 6.0.1
    • Version 6.0.1, up to but not including version 7.0
    • Version 7.0 up to but not including version 7.1
    • Version 7.1 up to but not including version 7.5
    • Version 7.5 up to but not including version 8.0
  • Set the preferences for the EGL Migration tool.

After the migration

After the migration tool finishes, you can review the changes that the tool made to the source code.

If you are migrating COBOL source or Rich UI projects, you might need to make more changes. For details, see COBOL-to-EGL migration" and "Rich UI project migration.

Note:
When you start using a new version of the product, use a new workspace to avoid problems. For example, changes in the set of available preferences can cause errors if you continue to use a workspace that was created with an earlier version of the product.