VisualAge Generator to Enterprise Generation Language Migration Guide

Associated program parts

VisualAge Generator: The program's associates can be in multiple projects and packages for VisualAge Java or in multiple configuration maps and applications for VisualAge Smalltalk.

EGL: The program's associates can be in multiple projects, folders, packages, and files.

Associated parts needed for migration: For a program: All associates.

Note:
See "EGL build path and import statements" for additional information on import statements.

Figure 32. Associated program parts

Migrating with the associated part
Migrating without the associated part
The migration tool does the following:
  • Includes a package statement to specify the package in which the EGL file is to be placed.
  • Includes import statements in the EGL file for any packages that contain associates needed by any of the parts in the current file and which are in a different package from the current file. The import statements are only included if you migrate using Stages 1 through 3.
  • For the program the migration tool does the following:
    • Includes a declaration for the program's primary working storage record. If there are level 77s in the VAGen primary working storage record, the tool also includes a declaration for the new level 77 item record.
    • Includes declarations for all records in the VAGen Tables and Additional Records list, including the redefines property, if applicable, for any VAGen redefined records.
    • Includes declarations for all I/O records.
    • Includes declarations for records used as parameters on MQ API calls (the records specified as attributes of an MQ Message record in VisualAge Generator).
    • Includes use declarations for any tables in the VAGen Tables and Additional Records list.
    • Includes use declarations for the program's map group and help map group.
The migration tool makes use of all program associates that are available.
Potential problem: None.

Potential Problem 1: A problem only arises if there are missing parts. If the migration tool detects missing parts, it issues a warning message that identifies the missing parts. The migration tool does not make any assumption about the missing part(s). This can result in a variety of problems in the migrated program, including the following:

  • Missing import statements.
  • Missing level 77 record declaration.
  • Missing redefines property for VAGen redefined records.
  • Missing I/O record declarations.
  • Missing declarations for records used as parameters on MQ API calls.

Except for the missing redefines property, there will be errors on the Tasks list to help you identify the problem(s). Note: the migration tool does not detect all missing parts.

Possible Solution 1A: Change your migration set to include all the parts that are needed to validate the program in VisualAge Generator. Migrate the program again using the new migration set so that all the program's associates are migrated together.

Possible Solution 1B: Locate the missing parts in EGL and correct the EGL program.

Potential Problem 2: For missing level 77 items, see Level 77 items in records .

Potential Problem 3: For missing redefined records, see Redefined records .


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