When you migrate from a version earlier than version 7.0,
you must migrate to all of the versions between your version and version
7.0.
For example, to migrate from version 6.0, interim fix 001:
- Complete the appropriate tasks in the "Before you begin" section
of Migration from a previous version of EGL.
- Cancel the workspace migration
- Migrate to 6.0.1
- Migrate to 7.0
- Migrate the workspace
The following table shows the migration steps for each version.
To migrate, you must complete all of the necessary steps.
Updating the workspace
If you
are migrating from version 5.1.2, you might need to update the projects
in your workspace so that the workspace can migrate. You can do this
in either of two ways:
- Check the project into a repository
- Create a project interchange file
Canceling the workspace migration
When
you migrate from a version earlier than 7.0, you migrate the workspace
after code migration is complete. If you migrate the workspace too
early, some of the necessary migration will not occur. The workspace
migration wizard starts automatically when you start the product;
you must cancel this wizard.
To cancel the workspace migration:
- When the wizard starts, click Cancel.
- Right-click the projects that require migration, and click Close
project.
Migrating to version 6.0 iFix 001
Migrate
the code to version 6.0 iFix 001 by using the EGL V6.0 migration tool.
Note: Do
not use the migration tool on code that was updated to EGL version
6.0 interim fix 001, because this tool can cause errors in your code.
You
can use the migration tool on an entire project, a single file, or
a selection of files. If you run the tool on a package or folder,
it converts all of the EGL source files in that package or folder.
- Verify that the preferences for the migration tool are set. For
more information, see “Setting the EGL migration tool preferences.”
- In the Project Explorer view, select the EGL projects, packages,
folders, or files to migrate.
- Right-click the selected resources and then click .
- Optional: To avoid migrating the same code twice, disable the
V6.0 migration capability.
Results
Review the changes that the tool made
to the source code:
- In the Project Explorer view, right-click an EGL source file that
was migrated and then click .
- Examine the differences between the file in the workspace and
the previous version.
- When you finish reviewing the changes, click OK.
For more information about the code that the migration tool changes,
see “Changes made by the V6.0 iFix 001 migration tool.”
Migrating to version 6.0.1
To
migrate the code to version 6.0.1, manually complete the following
changes to the code:
- Make sure that none of your identifiers, such as variable or part
names, begins with the at symbol (@), which is now
an operator.
- Check the invocations of the following system functions. If the
last argument in an invocation is a numeric value (as evidenced by
an error message that indicates a problem with the primitive type
of the argument), change the invocation.
Table 2. Manual changes
to system functions| Old function |
New function |
| StrLib.compareStr |
VGLib.compareBytes |
| StrLib.CopyStr |
VGLib.copyBytes |
| StrLib.concatenate |
VGLib.concatenateBytes |
Migrating to version 7.0 and above
Use
the EGL V7.0 migration tool to migrate code from EGL version 6.0.1
or later to version 7.0 and up.
Note: Do not
use the migration tool on code that has already been migrated to EGL
V7.0. Doing so can create errors in your code.
You can use
the migration tool on an entire project, a single file, or multiple
files. If you run the tool on a package or folder, it converts all
of the EGL source files in that package or folder.
- Verify that the preferences for the migration tool are set. For
more information, see "Setting the EGL migration tool preferences."
- In the Project Explorer view, select the EGL projects, packages,
folders, or files to migrate. You can select any number of EGL resources
to migrate. To select more than one resource at once, press and hold
Ctrl while you click the resources.
- Right-click a selected resource and then click .
- Check your code for errors and for places that do not comply with
EGL V7.0. You might need to make manual changes to your code. For
more information, see “Changes not made by the V7.0 migration tool.”
- Optional: To avoid migrating the same code twice, disable the
V7.0 migration capability.
Results
Review the changes that the tool made
to the source code:
- In the Project Explorer view, right-click an EGL source file that
was migrated and then click .
- Examine the differences between the file in the workspace and
the previous version.
- When you are finished reviewing the changes, click OK.
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.”
Migrating the workspace
To
migrate the workspace for a project:
- Right-click the projects to be migrated.
- Click Open Project.
- Migration is automatic. If you are migrating web projects from
version 6, you must migrate them to version 7 before opening them
in version 8.