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.
Figure 32. Associated program parts
Migrating with the associated part
| Migrating without the associated part |
---|---|
The migration tool does the following:
| 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:
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 .
|
(C) Copyright IBM Corporation 1992, 2005. All Rights Reserved.