VisualAge Generator: A numeric field on a map has one length. The length should be long enough to allow for all the digits, the decimal point, sign, currency symbol, and numeric separator. However, if the field is not long enough at runtime, VisualAge Generator omits the currency symbol and numeric separator. VisualAge Generator also omits the sign if it is positive. If necessary to fit into the space allowed, VisualAge Generator drops the high order digits.
EGL: Variable fields on a form specify both a type definition, which includes the number of digits and decimals, and a fieldLen that specifies the space that the data occupies on the form. If the fieldLen is not big enough to contain all the digits and formatting characters at runtime, EGL issues a runtime message.
Associated part needed for migration: Not
applicable.
Figure 23. Numeric variable fields
Migrating with the associated part | Migrating without the associated part |
---|---|
When migrating a numeric field on the map, the migration tool sets the
length and fieldLen as follows:
| The migration tool does the same thing as mentioned in the Migrating with the associated part column. |
Potential Problem: If the field length on the form is not large enough at run time to contain all the digits, decimal point, sign, currency symbol, and numeric separator characters, EGL issues a run time error message. Solution: Change the form definition so that the fieldLen
is large enough to contain the largest possible number that will occur at run
time and all the formatting characters that you specify.
| The same problem listed under the Migrating with the associated part column can occur. You can use the same solution. |
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.