VisualAge Generator to Enterprise Generation Language Migration Guide

Stage 1 on VisualAge Smalltalk

The following messages occur only in the VisualAge Smalltalk version of the VisualAge Generator to EGL migration tool.

HPT.EGL.0201.e Current application name vagenApplicationName - results in EGL package name eglPackageName, which starts with # or uses reserved word(s) reservedWordList. It must be renamed.

Explanation: EGL reserved words cannot be used as any word in the dot notation for EGL package names.

User Response: Use the Stage 1 renaming rules to create an EGL package name that does not violate the EGL naming restrictions. Refer to Appendix Reserved words that lists the EGL reserved words. Be sure that the resulting EGL package name does not start with the # symbol.

HPT.EGL.0202.eMigration set migrationSetName references Configuration map configurationMapName, which is not defined in the repository.

Explanation: The Stage 1 migration tool expanded the high-level configuration map for the specified migration set. However, when the tool expanded the high-level configuration map and the chain of required maps and applications, one or more required maps was not available in the library.

User Response: Determine whether the required map should be included in the migration set. If so, check to see whether the requested version of the configuration map has been purged from the library. If so, salvage the requested configuration map and then migrate again.

HPT.EGL.0203.e ProgramContext encountered a database error errorMessage.

Explanation: A database error occurred. Possible problems are invalid schema name, user authority restrictions, or missing tables.

User Response: Correct the migration preferences file. If the problem persists, contact IBM support for assistance.

HPT.EGL.0204.e An error occurred while connecting to the database. ErrorMessage.

Explanation: A database error occurred on connect. Possible problems are invalid userid or password name or invalid database name.

User Response: Correct the migration preferences file. If the problem persists, contact IBM support for assistance.

HPT.EGL.0205.i Migration produced n migration sets from the v versions of configuration map configMapName. The preference file specified the version depth as d.

Explanation: The Stage 1 migration preferences file specified that you wanted to migrate the number of versions specified by d. The Stage 1 migration tool should have produced d migration sets -- one for each version of the specified configuration map. However, the migration tool only created the number of migration sets specified by n. The number specified by v is the number of versions of the specified configuration map that the migration tool found in the library. If v is less than d, this means that there were not as many versions of the configuration map as you anticipated. In this case, n and v should be equal, indicating that all the configuration map versions resulted in migration sets. If v is greater than d, this means that there are more versions of the configuration map in the library. In this case, n and d should be equal, indicating that your version depth preference was met.

User Response: None.

`````````````````````````````````````````````````````````


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