VisualAge Generator to Enterprise Generation Language Migration Guide
There are some situations in which the External Source Format produced
after running the Stage 1 migration tool will cause problems when running the
migration tool that produces EGL. Those situations, which are very rare
and unlikely, are discussed here.
-
Data item part
-
The map range edit (minimum and maximum values) can cause an exception in
Stage 2 due to invalid External Source Format. The problem occurs if
External Source Format is imported into VisualAge Generator and the data item
is never modified. When the External Source Format is exported in Stage
1 of the migration, the map range edit is in an invalid format. Modify
the data item in VisualAge Generator and save the item. For example,
add and remove a blank from the item description. Alternatively,
before you run Stage 1 of migration, install the fix for VisualAge
Generator APAR PQ75621 or APAR PQ79914.
- For VisualAge Generator on Java, data items with similar part names can
cause unpredictable results when the # symbol is used in one of the
names. For example, DATAITEM#A, DATAITEM@A, and DATAITEM$A can result
in the wrong External Source Format code being stored in the migration
database for DATAITEM#A. If you have used the # symbol in data item
names, review the resulting EGL source code to ensure that the correct
information was migrated. Alternatively, before you run Stage 1 on
Java, install the fix for VisualAge Generator APAR PQ85794.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.