VisualAge Generator to Enterprise Generation Language Migration Guide

Stage 1 common messages

The following messages are common to the VAGen migration tool on both VisualAge for Java and VisualAge Smalltalk

HPT.CM.215.eFile filename cannot be opened. The return code is returnCode (returnCodeText).

Explanation: The specified file cannot be opened. The returnCode and returnCodeText indicate the reason why. returnCode 2 indicates the file cannot be found.

User Response: Provide a valid file for the migration tool.

HPT.EGL.0001.wTable name tableName is a reserved word. It must be renamed.

Explanation: The migration tool does not rename tables for you.

User Response: You must change the name of the table and all references to it, including references in any program's table and additional records list, logic statements, data item edit routines, and map edit routines. Be sure to change any non-VAGen references to the table name, including CICS program definitions. Alternatively, you can wait until you have migrated, rename the table in WebSphere Studio, and use the EGL alias property to specify the original table name.

HPT.EGL.0002.w Map group name mapGroupName is a reserved word. It must be renamed.

Explanation: The migration tool does not rename map groups for you.

User Response: You must change the name of the map group, the names of all maps in the map group, and all references to the map group, including references as any program's map group or help map group. Be sure to change any non-VAGen references to the map group name, including CICS program definitions. Alternatively, you can wait until you have migrated, rename the form group in WebSphere Studio, and use the EGL alias property to specify the original map group name.

HPT.EGL.0003.w Program name programName is a reserved word. It must be renamed.

Explanation: The migration tool does not rename programs for you.

User Response: You must change the name of the program and all references to it, including references on CALL, DXFR, and XFER statements. Also change the names of any bind control or linkedit parts that correspond to this program. Be sure to change any non-VAGen references to the program name, including CICS program definitions. Alternatively, you can wait until you have migrated, rename the program in WebSphere Studio, and use the EGL alias property to specify the original program name.

HPT.EGL.0004.w Control part name partName is a reserved word. It must be renamed.

Explanation: The specified control part name uses dot notation, where the name before the dot is a reserved word. The migration tool assumes that the name before the dot is a program name and that this control part is closely tied to a program. Because the migration tool does not rename programs, it also does not rename control parts that are in dot notation.

User Response: You must change the name of the program and all references to it, including references on CALL, DXFR, and XFER statements. Also change the names of any bind control or linkedit parts that correspond to this program. Be sure to change any non-VAGen references to the program name, including CICS program definitions. Alternatively, you can wait until you have migrated, rename the program in WebSphere Studio, and use the EGL alias property to specify the original program name. Refer to Appendix Reserved words that lists the EGL reserved words.

HPT.EGL.0005.w UI Record partName is a reserved word or starts with the # symbol. It must be renamed.

Explanation: The specified UI record conflicts with the EGL naming conventions. This release of EGL does not support web transactions or UI records. The Stage 1 migration tool includes the UI record in the migration set. The Stage 2 and 3 migration tools filter out the UI records, without migrating them to EGL source.

User Response: None. There is no need to rename the UI record in VisualAge Generator. The expectation is that the Stage 2 and 3 migration tools will handle renaming for UI records just as they do for other records.

HPT.EGL.0006.iMigration of preferenceFile will produce outputList.

Explanation: Migration of preferenceFile will produce outputList. Possible outputs are migration plans, report, and database updates.

User Response: None.

HPT.EGL.0007.wNo migration files were created based on the current filters.

Explanation: No migration files were created based on the current filters.

User Response: Change the filter preferences.

HPT.EGL.0008.ePreferenceValue is an invalid value for preference option preferenceOption.

Explanation: The value is invalid for the preference option.

User Response: Changes the preference option value in the preferences file.

HPT.EGL.0009.eMigration set migrationSetName requires the preferences for the spanning maps suffixes be specified.

Explanation: The specified migration set contains one or more map groups that span multiple projects or multiple packages. The migration tool requires you to specify the spanning maps suffix preferences so that it can create the project or package necessary for the map group.

User Response: Edit the Stage 1 migration preferences file. On the Mapping page, in the Spanning Maps section, specify values for the Project suffix and Package suffix fields. See Mapping page for Java or Mapping page for Smalltalk for more details.

HPT.EGL.0010.wNo migration action was requested.

Explanation: You have not selected any output options for the Stage 1 migration tool.

User Response: Select one or more options. The options enable you to create a migration plan file, create a report, or update the database.

HPT.EGL.0011.iStarting the database clean up of migration set migrationSetName.

Explanation: The migration database already contained information for the specified migration set. The migration tool deleted the migration set information in preparation for running Stage 1 with a new set of preferences.

User Response: None.

HPT.EGL.0012.iCompleted the database clean up of migration set migrationSetName.

Explanation: The migration database already contained information for the specified migration set. The migration tool deleted the migration set information in preparation for running Stage 1 with a new set of preferences.

User Response: None.

HPT.EGL.0013.eEach renaming rule must have a unique order value.

Explanation: Two or more renaming rules have the same order number.

User Response: Edit the Stage 1 migration preferences file and change the renaming rules so that each rule has a unique order number.

HPT.EGL.0014.i Migration set migrationSetName-migrationSetVersion produced n error messages, n warning messages, and n informational messages.

Explanation: n is the number of messages issued by the Stage 1 migration tool for the specified migration set. The count for the informational messages includes message HPT.EGL.0014.i.

User Response: None.

HPT.EGL.0015.eDerived EGL project name eglProjectName contains invalid character(s): characterList.

Explanation: Using the renaming rules that you specified, the Stage 1 migration tool has created a proposed EGL project name that does not meet the EGL project naming conventions. The characters that are invalid shown in the characterList.

User Response: Edit the Stage 1 migration preferences files and modify the project renaming rules so that they result in valid EGL project names. When you modify the renaming rules, be sure to consider the effect of any renaming rules that specify a Mapping Context of both.

HPT.EGL.0016.eDerived EGL package name eglPackageName contains invalid character(s): characterList.

Explanation: Using the renaming rules that you specified, the migration tool has created a proposed EGL package name that does not meet the EGL package naming conventions. The characters that are invalid shown in the characterList.

User Response: Edit the Stage 1 migration preferences files and modify your package renaming rules so that they result in valid EGL package names. When you modify the renaming rules, be sure to consider the effect of any renaming rules that specify a Mapping Context of both.

HPT.EGL.0017.eDerived EGL project name eglProjectName cannot end with a period (.).

Explanation: Using the renaming rules that you specified, the migration tool has created a proposed EGL project name that ends in a period. This name does not meet the EGL project naming conventions.

User Response: Edit the Stage 1 migration preferences files and modify your project renaming rules so that they result in valid EGL project names. When you modify the renaming rules, be sure to consider the effect of any renaming rules that specify a Mapping Context of both. Also consider the effect of any renaming rules that specify a String Context of any, back or token.

HPT.EGL.0018.eDerived EGL package name eglPackageName cannot begin with a digit or end with a period (.).

Explanation: Using the renaming rules that you specified, the migration tool has created a proposed EGL package name that ends in a period or begins with a digit. This name does not meet the EGL package naming conventions.

User Response: Edit the Stage 1 migration preferences files and modify your package renaming rules so that they result in valid EGL package names. When you modify the renaming rules, be sure to consider the effect of any renaming rules that specify a Mapping Context of both.

HPT.EGL.0019.iThe Migration Feature featureName versionName is loaded.

Explanation: This informational message provides the migration feature name and version that is currently loaded into your Java workspace or Smalltalk image.

User Response: None.

HPT.EGL.0020.iThe Migration Feature featureName versionName is not loaded. listOfNames are not loaded.

Explanation: This informational message provides the migration feature name and version that should be added to your Java workspace or loaded into your Smalltalk image. However, one or more Java packages or Smalltalk applications are not at the version expected for the migration feature. The listOfNames provides the list of Java packages or Smalltalk applications that are currently loaded but which are not at the expected version.

User Response: If you have not modified the Stage 1 migration tool, try adding the migration feature again for Java or loading the migration feature again for Smalltalk. If you have modified the Stage 1 migration tool, then this message serves as a reminder of the Java packages or Smalltalk applications that you have modified.


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