VisualAge Generator to Enterprise Generation Language Migration Guide

Precise EGL Syntax

Even though the syntax of the two languages differs greatly, the VAGen language can, for the most part, be migrated to the EGL language while preserving the same behavior as the original VAGen program. However, there are number of situations in which the EGL syntax is more precise or more restrictive than in VisualAge Generator. These situations are rare in typical programs. However, when they do occur, the migration tool requires cross-part migration to determine the exact EGL syntax that preserves the behavior you required in VisualAge Generator. Cross-part migration means that the migration tool needs to have one or more other referenced parts available to be able to do a correct migration of the current part. The following are some examples:

The migration tool uses all the available parts in the migration set to resolve ambiguous situations. To minimize these ambiguous situations, always include associated parts when you migrate. For example, when you migrate a program, be sure to include all the parts that you need to generate the program in VAGen. This ensures the best possible migration of your parts. For an overview of how the migration tool resolves ambiguous situations, see the following sections:

See the chapter Handling ambiguous situations for a complete list of the situations where the migration tool must do cross-part migration to achieve a correct migration and the steps the migration tool takes to try to make an intelligent choice if the additional parts are not available.


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