The first time the shared data item 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 EGL equivalent 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 the edit routine is not specified but the edit message
is specified, the migration tool sets the validatorTableMsgKey to
the edit message.
- Note:
- Even when migrating in program context, the editRoutineName might not be
available if the shared item is not used on a map or if its edits on the map
differ from what was specified in the shared item definition.
|
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.
- Otherwise, the migration tool sets the validator property and issues an
error message.
If the edit routine is not specified but the edit message
is specified, the migration tool sets the validatorTableMsgKey to
the edit message.
|
Potential Problem: A problem only arises if a VAGen
function and table have the same name, most likely in different
subsystems. In this situation, one subsystem uses a function and
another subsystem uses a dataTable. The problem does not occur until
the item is added to a text form.
Possible Solution 1: Rename the dataTable so there are no
longer two parts with the same name. Specify both a validator and
validatorTable property for the item definition. If you add the item to
a text form, delete the validator or validatorTable property, whichever is not
needed for that particular form. Disadvantage: You must modify
your programs and forms to use the new dataTable name.
Possible Solution 2: Set both validator and validatorTable
properties to the same name. Disadvantage: the data item
definition is always listed as an error on the Tasks list.
|
Potential Problem 1: A problem arises if the migration
tool guesses incorrectly. The problem does not occur until the item is
added to a text form.
Possible Solution: Correct the data item
definition.
Potential Problem 2: The same problem listed under the
Migrating with the associated part column can also occur.
You can use the same solutions.
|