EGL-to-EGL migration

The EGL V6.0 migration tool converts EGL source from V5.1.2 and V6.0 to comply with the EGL V6.0 iFix. Additional changes for EGL V6.0.1 are described in full at the end of this topic.
Note: Do not use the migration tool on code that has already been updated to the EGL V6.0 iFix. Doing so can create errors in your code.

The migration tool can be used on an entire project, a single file, or a selection of files. Running the tool on a package or folder converts all of the EGL source files in that package or folder. For instructions on how to use the migration tool, see Migrating EGL code to EGL 6.0.1.

The migration tool can add comments to each file it changes, and it can also add comments to the project's log file. To change these options, see EGL-to-EGL migration preferences.

The migration tool changes EGL code in these ways to comply with the EGL V6.0 iFix:

After you use the EGL V6.0 migration tool, make sure that none of your identifiers (such as variable or part names) begins with the at sign (@), which is now used as the first character of a complex property. Also, if you migrated code from VisualAge® Generator, you may need to change StrLib.compareStr to VGLib.compareBytes, StrLib.copyStr to VGLib.copyBytes, and StrLib.concatenate to VGLib.concatenateBytes; but a change is needed only when the last argument in the existing invocation is a numeric value, as evidenced by an error message that indicates a problem with the argument's primitive type.

Related tasks
Migrating EGL code to EGL V6.0 iFix

Related concepts
Setting EGL-to-EGL migration preferences
Changes to properties during EGL-to-EGL migration

Related reference
EGL reserved words

Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.