VisualAge Generator to Enterprise Generation Language Migration Guide


Tables

The VAGen tables section is organized into the following tables:


Figure 70. Tables -- general syntax, table type, properties, and prolog

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
VAGen table part:
  • tableName
  • Basic information
    • Table type
    • Table structure (item list)
  • Properties
  • Prolog
  • Table Contents
EGL syntax example:
//*** DataTable=tableName***
// prolog
//******************* 
DataTable tableName
  type tableType
  { [otherTableProperties]
  [alias =
    "originalTableName"] }
  tableStructure
  [{ contents =
    [{rowContents}] }]
end  // end tableName
The migration tool does not rename tables for you even if they conflict with the EGL reserved word list. The migration tool does not set the alias property. If you must rename a table, you can use the alias property to specify the original name of the VAGen table. See information about table names in Reserved words and table names for details.
Table types:
  • Unspecified
  • Match Invalid
  • Match Valid
  • Range Match Valid
  • Message
DataTable types:
  • basicTable
  • matchInvalidTable
  • matchValidTable
  • rangeChkTable
  • msgTable
No special considerations.
Properties -- Runtime attributes:
  • Resident
  • Shared
DataTable properties:
  • resident
  • shared
No special considerations.
Properties - Fold table contents Not applicable. If you want the table contents to be folded, you must enter the contents in upper case. If the VAGen table specifies that the table contents should be folded, the migration tool ensures that the char, hex, and mixed data in the table contents is converted to upper case.
Prolog Not applicable. The migration tool converts the prolog to a comment that precedes the DataTable definition.

Figure 71. Tables -- Table structure

VisualAge Generator 4.5 EGL produced by the migration tool Migration tool considerations
VAGen Table structure - with Shared Items:
  • itemName
  • Shared
  • levelNumber
    Note:
    levelNumber is hidden, but it is based on the data item hierarchy within the record.
Note:
Type, Length, Decimals and Description are visible in the table editor, but are not stored in the table.
DataTable structure - with EGL type definitions:
levelNumber itemName 
            itemName ;
Note:
Type, Length, Decimals and Description are not visible in the editor.
The migration tool migrates shared items to an EGL variable that is defined using a type definition. For migration, the type definition is always the same as the item name.
VAGen Table structure -- with Nonshared Items:
  • itemName
  • Type
  • Length
  • Decimals
  • Nonshared
  • Description
  • levelNumber
    Note:
    levelNumber is hidden, but it is based on the data item hierarchy within the table.
Note:
Type, length, decimals, and description are stored with the item in the table.
DataTable structure -- with EGL primitive types:
levelNumber itemName 
  dataType(lengthInformation) ;
       // Description
Note:
Type, length, decimals and description are visible in the editor.
The migration tool migrates nonshared items to an EGL variable that is defined using a primitive type. Migration of type, length, and decimals information is the same as described in Figure 61.

Figure 72. Tables -- table contents

VisualAge Generator 4.5 EGL produced by the migration tool Migration tool considerations
Table contents:
  • Table contents are entered in a formatted editor. Table contents are entered for the top level (parent) items in the table structure.
  • Character and hex data is not enclosed in quotes.
DataTable contents:
  • Each row's contents is enclosed in square brackets. There is an outer set of square brackets that encloses the entire set of rows.
  • Values within the row contents must be separated by commas.
  • Character data including hex data must be enclosed in double-quotes.

Example:

contents = [ [ rowContents ] 
         { , [ rowContents ] }
  ]
where
  rowContents = value { , value}

If the VAGen table specifies that the table contents should be folded, the migration tool ensures that the char, hex, and mixed data in the table contents is converted to upper case.

The migration tool also encloses character data, including hex data, in double-quotes.


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