VisualAge Generator to Enterprise Generation Language Migration Guide

Map arrays and attributes

VisualAge Generator: VisualAge Generator permits, but does not recommend, using different attributes for the elements of an array. For example, in VisualAge Generator the protection, input required, require fill on input, numeric hardware attribute, modified data tag, and light pen detect can vary for each element of the map array.

EGL: In EGL, the only properties that can be overridden for an array item are the field presentation properties (color, highlight, intensity, and outline) plus cursor, position and value.

Associated part needed for migration: Not applicable.

Figure 26. Map arrays and attribute fields

Migrating with the associated part Migrating without the associated part
The migration tool uses the following properties for the first element of the array (array index 1) to set the EGL equivalent properties: protection, input required, require fill on input, numeric hardware attribute, modified data tag, and light pen detect. EGL uses the properties for the first element of the array for all the elements of the array. The migration tool does the same thing as mentioned in the Migrating with the associated part column.

Potential Problem: A problem only arises if you used different attributes for the elements of the array.

Possible Solution: Change the properties for the first element of the array to the least restrictive values and add logic in a validator function to verify that each element of the array meets the necessary criteria. Also notify your end users of any differences in the appearance of the form at runtime.

The same problem listed under the Migrating with the associated part column can occur. You can use the same solution.


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