VisualAge Generator to Enterprise Generation Language Migration Guide

Map group and formGroup requirements

VisualAge Generator: A map group is only required if there is a floating area specification.

EGL: A formGroup is always required to contain the forms.

Associated part needed for migration: The map group and all maps in the map group.

Figure 19. Map group and formGroup requirements

Migrating with the associated part
Migrating without the associated part
If a map group does not exist, the migration tool does the following:
  • Creates a formGroup for all maps with the same map group name.
  • Puts all the forms for the same formGroup in the same EGL file.
  • Nests the forms within the formGroup definition if not migrating with single file migration.
  • Issues an error message indicating that the formGroup requires editing to nest the forms if migrating in single file mode.
The migration tool does the same things mentioned in the Migrating with the associated part column. However, if you do not have the map group and all its maps in the same migration set, there can be problems as described below.

Potential Problem: None. All maps for the map group should be included in the same migration set. Because the migration set represents what is generated, the migration set should include all maps in the map group.

If you are migrating in single file mode, be sure to include all the maps in the map group in the same External Source Format file.

Potential Problem: If all maps for the same map group name are not included in the same migration set (or External Source Format file for single file mode migration), the formGroup will not include all the forms.

Possible Solution 1: Be sure the migration set includes all maps with the same map group name.

Possible Solution 2: Add the missing forms to the EGL file and nest them within the formGroup definition.


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