VisualAge Generator to Enterprise Generation Language Migration Guide


Chapter 3. Handling ambiguous situations

There are a number of situations where the migration tool might not have all the information from VisualAge Generator needed to produce the corresponding EGL statement. These situations are called ambiguous situations because the corresponding EGL statement could change or produce different results depending on the inputs from VisualAge Generator. In these ambiguous situations, the migration tool might not migrate to EGL statements that match what you intended in VAGen. In many of the ambiguous situations, the EGL statements that are produced vary, depending on your migration process:

Migrating with a program and its associates is the preferred way of migrating with associates because it guarantees the maximum information. The tables that follow explain the differences between migrating with and without associated parts for the following part types:

The tables also show some potential problems that can arise for these ambiguous situations and suggest possible solutions for these problems. No one solution is best for every situation. For example, when there are two parts with the same name, renaming the one that is the least frequently used would have the least effect in other areas of your code.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]