VisualAge Generator to Enterprise Generation Language Migration Guide


Map groups

The map groups section is organized into the following tables.


Figure 73. Map Groups -- general information

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
The map group part is only required if there are floating areas.

If there is no map group part, VisualAge Generator automatically generates all maps with the same map group name as though the map group part did exist.

The formGroup is required. The migration tool creates a formGroup part if one does not exist in the migration set.
Map names consist of a map group name and a map name.

The form name does not include the formGroup name.

A form can be defined (nested) within a form group.

Alternatively, a form can be outside the formGroup part. In this case, the formGroup part must include a use statement to specify the form name and an import statement import the package in which the form located. This technique enables you to have one definition of a common form (for example, a pop-up list form) and make it available in many different form groups.

The migration tool migrates all maps to forms. The tool does not attempt to identify common, identical map definitions across multiple map groups.

If you migrate in single file mode, the migration tool includes a use statement for each form within a form group. You should move the forms so that they are nested within their formGroup part.

If you migrate using Stage 1 - 3 migration, the migration tool automatically nests all forms within the formGroup part.

When a program specifies a map group, the program can use any map within the map group just by referencing the map name. When a program includes a use statement to indicate which formGroup it is using, the program can reference any map within the formGroup just by referencing the form name. No special considerations.

Figure 74. Map Groups -- general syntax and floating areas

VisualAge Generator 4.5
EGL produced by the migration tool Migration tool considerations
The map group part can contain the following:
  • Map group name
  • Floating area information
    • Device name
    • Device size
    • Size
      • Lines
      • Columns
    • Position
      • Starting line
      • Starting column
The formGroup part can contain the following:
  • Form group name
  • Form group properties
  • Screen floating area information
  • Print floating area information
  • Use statements for the forms that are included in the form group.

An example of the format of a form group part is as follows:

FormGroup groupName {
 [ alias="generationName"]
 [ screenFloatingArea
   {screenFloatingAreaInformation}]
 [printFloatingArea
   {printFloatingAreaInformation}]
 Form formName type textForm
  {formProperties}
   [variableFields]
   [constantFields] 
  end // end formName
  use formName2;
end // end groupName 

The migration tool uses the VAGen device type to determine whether the floating area information is for a Display map (screenFloatingArea) or a Printer map (printFloatingArea).

See Figure 75 about setting deviceType.

Not applicable. alias The migration tool does not rename map groups even if they conflict with an EGL reserved word. Special considerations apply. See Reserved words and formGroup names for details and potential problems.
Floating area information includes the following:
  • Device name
  • Device size (rows x columns)
  • Floating area specification
    • Size
      • Lines
      • Columns
    • Position
      • Starting line
      • Starting column
Note:
  • In VisualAge Generator, you define the size and starting position of the floating area.
  • Different floating area specifications are permitted, but not recommended, for devices that have the same size.
Floating area information includes the following:
  • Device size
  • Margin information
Print floating area information also includes the device type.

Here is an example of the screen floating area that is used for text forms:

screenFloatingArea {
 screenSize=(lines,columns)
 topMargin=nn,
 bottomMargin=nn,
 leftMargin=nn,
 rightMargin=nn
 } 

Here is an example of the print floating area that is used for print forms:

printFloatingArea {
 deviceType=singleByte,
 pageSize=(lines,columns)
 topMargin=nn,
 bottomMargin=nn,
 leftMargin=nn,
 rightMargin=nn
 } 
Note:
Only one floating area specification is permitted for a screenSize or pageSize.

The migration tool uses the VAGen device type to determine whether the floating area specification is for display maps (screenFloatingArea) or print maps (printFloatingArea).

The migration tool computes the margin information as follows:

  • The topMargin is set to the VAGen floatingAreaStartingLine - 1.
  • The bottomMargin is set to the VAGen deviceRows - (floatingAreaStartingLine + floatingAreaLines) + 1.
  • The leftMargin is set to the VAGen floatingAreaStartingColumn - 1.
  • The rightMargin is set to the VAGen deviceColumns - (floatingAreaStartingColumn + floatingAreaColumns) + 1.

See Figure 75 for information about setting the deviceType.

Printer type can be one of the following:
  • Printer
  • DBCS printer
deviceType=singleByte | doubleByte
Note:
The deviceType property is only specifed for print forms.
The migration tool sets the EGLdeviceType property based on the VAGen printer type.

Figure 75. Map Groups -- device names, types, and sizes

VisualAge Generator Device Name
Device Size (lines x columns) Device Type Migration tool considerations
3643-2 6 x 40 Display This device size is not supported for COBOL generation.
3277-1 12 x 40 Display This device size is not supported for COBOL generation.
3643-4 16 x 64 Display This device size is not supported for COBOL generation.
3278-1, 3278-1B, ANY-1D 12 x 80 Display No special considerations.
3278-2, 3278-2B, ANY-2D 24 x 80 Display No special considerations.
3278-3, 3278-3B, ANY-3D 32 x 80 Display No special considerations.
3278-4, 3278-4B, ANY-4D 43 x 80 Display No special considerations.
3278-5, 3278-5B, ANY-5D 27 x 132 Display No special considerations.
ANY-D (3290 configured as 62x160) 255 x 160 Display This device size is not supported for COBOL generation.
5550D 24 x 80 DBCS Display No special considerations.
3767, PRINT-B, PRINTER 255 x 132 Printer For the printFloatingArea, the EGL deviceType=singleByte
5550P 255 x 158 DBCS Printer For the printFloatingArea, the EGL deviceType=doubleByte


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