VisualAge Generator to Enterprise Generation Language Migration Guide


Data items

The data items section is organized into the following tables:

Note:
There is only one set of edit and message properties for a data item. Even though this release of EGL does not support UI records, the migration tool merges the map and UI properties for the data items. The migration tool also converts the label and help UI properties to their EGL equivalent properties. This preserves as much of your data item information as possible. You can use this information if you develop any new EGL forms or page handlers.

Figure 61. Data items -- general syntax, data type, length, decimals, and description

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
VAGen data item part:
  • itemName
  • Basic information:
    • Data type
    • Length
    • Decimals
    • Description
  • Default Map Properties
  • User Interface (UI) Properties
EGL syntax example:
// Description
DataItem itemName 
  dataType(lengthInformation) 
  {  [ { formattingProperties } ]
     [ { validationProperties } ]
     [ { pageItemProperties } ]
  }
end

The migration tool uses the VAGen data type, length, and decimals to determine the EGL dataType and lengthInformation.

The migration tool merges the VAGen default map properties and the UI properties into the single set of EGL formatting, validation, and pageItem properties.

Character item types:
  • Char
  • Hex
  • DBCS
  • Mixed
  • Unicode (VisualAge for Java only)

Length is the number of characters. In the record editor you can also show the number of bytes.

Corresponding character item types:
  • char
  • hex
  • dbchar
  • mbchar
  • unicode

Length is the number of characters.

The migration tool converts character data items to the corresponding type and length.
Numeric character (zoned decimal) types:
  • Num
  • Numc

Length is the total number of digits, with a maximum of 18. Decimals is the number of digits to the right of the decimal point. In the record editor, you can also show the number of bytes.

Corresponding numeric types:
  • num
  • numc

Precision is the total number of digits, with a maximum of 18. Scale is the number of digits to the right of the decimal point.

The migration tool converts to the corresponding type, precision, and scale. The migration tool omits the scale if decimals is 0.
Packed decimal types:
  • Pacf
  • Pack

Length is the total number of digits, with a maximum of 18. Decimals is the number of digits to the right of the decimal point. The length for Pacf must be odd or 18. The length for Pack can be odd or even. Except for a length of 18, even lengths are recorded within the data item definition, but are treated as the next higher odd length for test, generation, and in the Data Item and Record editors. Only the SQL Record editor shows the even lengths and only SQL records support even length for test and generation. The even length is only used in SQL where clauses and in SQL functions that use execution time statement build. In the record editor you can also show the number of bytes.

Corresponding numeric types:
  • pacf
  • decimal

Precision is the total number of digits, with a maximum of 18. Scale is the number of digits to the right of the decimal point. The length for pacf must be odd or 18. The length for decimal can be odd or even. Even lengths are supported for data item definitions and all record types.

At test and generation, if you use VisualAge Generator Compatibility mode, EGL does the following for decimal items with even precision:

  • Increases the precision by one in all records.
  • EGL uses a temporary variable with the even precision in SQL where clauses or prepare statements.
The migration tool converts to the corresponding type, precision, and scale. The migration tool omits the scale if decimals is 0. For a Pack item, if an even length was recorded in the data item definition, the migration tool migrates it as the even length.
Binary item types:
  • Bin, length 4, no decimals
  • Bin, length 9, no decimals
  • Bin, length 18, no decimals
  • Bin, length 4, 9, or 18 with decimals
Corresponding binary types:
  • smallint (no precision or scale)
  • int (no precision or scale)
  • bigint (no precision or scale)
  • bin with precision and scale
The migration tool converts binary data items to the corresponding type based on the length and number of decimals. The bin type is only used if decimals (scale) is specified.
Description Not applicable. The migration tool converts the item description to a comment that precedes the DataItem definition.

Figure 62. Default map properties and User Interface properties - general information

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations

Data items can have both default map properties and user interface (UI) properties specified. The properties include the following:

  • formatting edits
  • validation edits
  • error messages

UI properties also include a label and help text.

Explicitly setting some properties in VisualAge Generator automatically causes other properties to be set. For example, setting numeric separator also explicitly sets fill character, input required, justify, currency symbol, and sign.

Data items can have the following properties:

  • formatting properties
  • validation properties
  • page item properties

The categories for some properties are changed from VisualAge Generator. For example, error messages are grouped with the validation properties. Page item properties include the UI label and help text. The EGL column in the following tables shows the category for the EGL property.

The migration tool merges the default map properties and UI properties, giving precedence to the UI properties. Validation edits and their associated error messages are migrated as a pair. The migration tool only migrates properties that were explicitly set in VisualAge Generator. The tool does not automatically insert default values for EGL properties. See information about Merging map and UI edits in Shared edits and messages for details and potential problems.

Also see information about map item edits for shared data items in Map item edit routine for shared data items for details and potential problems.


Figure 63. Default map properties and User Interface properties - general edits

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
Edit type (UI only) - values:
  • None
  • Boolean
  • Date
  • Time
EGL supports multiple properties:
  • not applicable
  • boolean = yes
  • dateFormat = locale
  • timeFormat = "hh:mm:ss"
(formatting properties)
No special considerations.
Edit function (UI only) validator (validation property) No special considerations.
Edit table (UI only) validatorTable (validation property) No special considerations.
Run edit function on web (UI only) Not supported. The migration tool converts to a comment. The comment includes the EGL runValidatorFromProgram property, which is expected to be the eventual replacement. The EGL property is the reverse of the VAGen property. The migration tool converts yes to no and no to yes when creating the comment.
Edit routine (map only) validator OR validatorTable

(validation property)

If the UI edit function and edit table are not specified, the migration tool does the following:
  • Sets the validator property if the map edit routine is EZEC10 or EZEC11.
  • Sets the validator property if the edit routine is a function.
  • Sets the validatorTable property if the edit routine is a table.

If the UI edit function or edit table are specified, the migration tool does not migrate the map Edit routine.

Special considerations apply if the edit routine is not available during migration. See information about map edit routines in Map item edit routine for shared data items for additional details and potential problems.

Justify - Left | Right | None (map only)
Note:
  • For map items, the default is right for numeric fields and left for all other fields.
  • For UI items, justify is not supported.
align = left | right | none

(formatting property)

Note:
  • For form fields, the default is right for numeric fields and left for all other fields
  • For page items, align is not supported.
No special considerations.
Date edit mask (map only)

Valid values are as follows:

  • SYSGREGRN
  • SYSJULIAN
  • dateEditPattern
dateFormat = value

Valid values are as follows:

  • systemGregorian
  • systemJulian
  • "dateEditPattern"

(formatting property)

If the UI edit type does not specify Date, the migration tool sets the dateFormat based on the Date edit mask specified in VisualAge Generator, if any. If the UI edit type specifies Date, the migration tool does not migrate the map Date edit mask.
Minimum input minimumInput (validation property) No special considerations.
Fill character
Note:
  • The default fill character for items used in a UI record is blank for character, MIXED, and numeric fields. The default fill character is zero for hex fields. Blank is the required fill character for DBCS and Unicode fields. Null is not a valid fill character.
  • The default fill character for items used on a map is null for character, DBCS, or MIXED fields. The default fill character is blank for numeric fields and zero for hex fields.
fillCharacter (formatting property)
Note:
The same default fillCharacter is used for both page items and form fields unless overridden in the specific page or form.
Special considerations apply because there is only one default fill character in EGL. See information about ambiguous data items and fill characters in Fill characters for shared data items for details and potential problems.
Fold upperCase (formatting property) No special considerations.
Hex edit (map only) isHexDigit (validation property) No special considerations.
Input required inputRequired (validation property) No special considerations.
Check SO/SI space needsSOSI (validation property) No special considerations.


Figure 64. Default map properties and User Interface properties - numeric edits

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
Minimum value and Maximum value
Note:
If either Minimum value or Maximum value is specified, both must be specified.
range = ( minimumValue, maximumValue ) (validation property) The migration tool combines the minimum and maximum value into the EGL range property.
Sign - None | Leading | Trailing
Note:
The default value is None.
sign = none | leading | trailing (formatting property)
Note:
The default value is none.
No special considerations.
Currency (both map and UI) Currency symbol (UI only)
currency = yes | no | 
    "currencySymbol" 

(formatting property)

Note:
  • The currencySymbol also applies to forms.
  • If currency = yes, the actual currency symbol used at runtime is set the same way it is in VisualAge Generator.
The migration tool migrates the first of the following that applies:
  • If the UI Currency symbol is specified, the tool migrates to currency = "currencySymbol".
  • If the UI Currency edit is set to yes or no, the tool sets the currency property to yes or no, respectively.
  • If the map Currency edit is set to yes or no, the tool sets the currency property to yes or no, respectively.
Separator numericSeparator (formatting property) No special considerations.
Zero edit zeroFormat (formatting property) No special considerations.

Figure 65. Default map properties and User Interface properties - error messages

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
Edit table (UI only) validatorTableMsgKey

(validation property)

No special considerations.
EZE function (UI only) validatorMsgKey (validation property) No special considerations.
Edit routine (map only) validatorTableMsgKey OR validatorMsgKey

(validation properties)

The migration tool only migrates the map edit routine message if the UI edit table, UI edit function, UI edit table message and UI EZE function messages are not specified. If the migration tool migrates the map edit routine message, the tool does the following:
  • Sets validatorMsgKey if the edit routine is EZEC10 or EZEC11.
  • Sets validatorTableMsgKey if the edit routine is a table.
  • Does not migrate the edit routine message if the edit routine is a function because the message is not used in this situation in VisualAge Generator.

Special considerations apply. See information about ambiguous data items and map edit routines in Map item edit routine for shared data items for additional details and potential problems.

Minimum input minimumInputMsgKey

(validation property)

No special considerations.
Input required inputRequiredMsgKey

(validation property)

No special considerations.
Data type typeChkMsgKey (validation property) No special considerations.
Numeric range rangeMsgKey (validation property) No special considerations.

Figure 66. User Interface properties - label and help

VisualAge Generator 4.5 EGL produced by the migration tool Migration tool considerations
UI label displayName (page item property) No special considerations.
Help text help (page item property) No special considerations.


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