VisualAge Generator to Enterprise Generation Language Migration Guide

Variable map fields and edit routines

VisualAge Generator: A map variable field can have an edit routine that is a table, a function, EZEC10, or EZEC11. The edit message is only used if the edit routine is EZEC10, EZEC11, or a table.

EGL: A form field can have both a validatorTable and a validator function. A form field can also have both a validatorTableMsgKey and a validatorMsgKey.

Associated part needed for migration: Either the table or function part.

Figure 24. Variable map fields and edit routines

Migrating with the associated part
Migrating without the associated part
The first time the map is migrated, the migration tool does the first of the following that applies:
  • If the editRoutineName is EZEC10 or EZEC11, the migration tool sets the validator property to the EGLequivalent system library function. The migration tool also sets the validatorMsgKey to the edit message, if any.
  • If the editRoutineName is a function, then the migration tool sets the validator property. The migration tool omits the validatorMsgKey because it is not used in VisualAge Generator.
  • If the editRoutineName is a table, then the migration tool sets the validatorTable property. The migration tool also sets the validatorTableMsgKey to the edit message, if any.
If a function or table with the same name as the editRoutineName is not available, the migration tool does the first of the following that applies:
  • If the editRoutineName is EZEC10 or EZEC11, the migration tool sets the validator property to the EGL equivalent system library function name. The migration tool also sets the validatorMsgKey to the edit message, if any.
  • If the editRoutineName is longer than 7 characters it must be a function name, so the migration tool sets the validator property. The migration tool omits the validatorMsgKey because it is not used in VisualAge Generator.
  • If an edit message is specified, the migration tool sets the validatorTable and validatorTableMsgKey.
  • If an edit message is not specified, the migration tool sets the validator property and issues an error message.

Potential Problem: A problem only arises if a VAGen function and dataTable have the same name (most likely in different subsystems) and two programs share the same formGroup (most likely in the same subsystem) and one program expects to use the function and the other program expects to use the dataTable.

Possible Solution: Review programs that share a formGroup. If the situation arises, create a separate formGroup to use the validatorTable. Disadvantage: There are now two formGroups to maintain.

Potential Problem: A problem only arises if the migration tool guesses incorrectly. Any program that uses this map might expect a table when the migration tool specified a function.

Possible Solution: Review the uses of maps that have error messages.


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