VisualAge Generator to Enterprise Generation Language Migration Guide
You need to perform the following steps regardless of whether you used
Stage 1 - 3 migration or single file migration:
-
Review and resolve the errors in the migration log or the "TODO" list
log. These errors reflect ambiguous situations that the migration tool
was not able to resolve. Modify your EGL source code to resolve these
errors. For example, if you used the VAGen RETR statement and did not
explicitly specify a search column, then if the table was not available during
migration, the EGL syntax includes EZE_UNKNOWN_SEARCH_COLUMN. You must
update your EGL source code with the correct search column name based on the
table definition. See Appendix D, "Messages on Tasks list or from the preprocessor" for help with resolving specific strings that the migration tool
uses when it creates intentionally invalid EGL syntax.
- If you have program, table, or form group names that are reserved words,
you must change the part name. If you generate COBOL, you might want to
set the alias property for the part to specify the original part
name. That will help you avoid having to change any external references
to the program, table, or form group.
-
Review and resolve any additional errors on the Tasks list. See IWN.xxx messages on the Tasks list for help in resolving common messages on the Tasks list that are
a result of the migration process.
- Determine if you need to set the containerContextDependent
property for any records or functions. For more details, see containerContextDependent Property .
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.