APAR status
Closed as documentation error.
Error description
Rational Business Developer V7.5.1.4: Using the stage 1 migration tool, the following are error cases that are received which are not currently documented in the VisualAge Generator to EGL Migration Guide. Note: The problem resolution only documents the new cases to be added. Refer to the VisualAge Generator to EGL Migration Guide for the cases that are documented already. 1) Problem: HPT.EGL.0109.e An unexpected exception occurred: javaExceptionStackTrace. Problem Resolution: - If javaExceptionStackTrace indicates that there was a java.lang.NullPointerException: - If you are running the either the Preferences Tool or the Migration Tool, make sure that the following directory: vajavaInstallDirectory\ide\features\com-ibm-vgj-mig\pro jects.dat.pr\IBM VisualAge Generator EGL Migration\vers ion\data contains the following files: - MigPreferences.dtd - MigPreferences.xml - tableNodes.xml - VGMigrationDef.dtd Files might be missing if you installed VisualAge Java and VisualAge Generator and used long directory names or a directory name that contains spaces. Try unzipping the migration tool to another directory and copying the missing files to the product directory. Alternatively, try reinstalling both VisualAge Java and VisualAge Generator using a short directory name (for example, vag). - If you are running the Migration Tool and the details of the stack trace mention com.ibm.vgj.mig.XMLFileParser.readXML, com.ibm.vgj.mig.ConfigPlanEntity, and com.ibm.vgj.mig.VAGenToEGLMigration.loadConfigPlans, check that you have a valid migration plan file (.pln file). Also check whether you are using the -o option. This error can occur if you omit the -o option and the existing .pln file is empty or invalid. To correct the problem, either create a valid .pln file by hand or specify the -o option so that the migration tool creates a new (valid) .pln file for you. See "Running the Stage 1 tool" for details on the -o option. See "Creating a migration plan file manually" for details on how to create the .pln file by hand. - If javaExceptionStackTrace contains the following SQL message, check your system environment variables as described for message HPT.EGL.0104.e. SQL0444N Routine "routine-name" (specific name "specific-name") is implemented with code in library or path "library-or-path", function "function-code-id" which cannot be accessed. Reason code: "code". For example, ensure the PATH system environment variable includes sqlInstallationDirectory\SQLLIB\FUNCTION directory if the message indicates the path "\db2clifn" cannot be accessed. The db2clifn.dll is found in that directory. 2) Problem: HPT.EGL.0104.e An error occurred while connecting to the database. database: jdbc:DB2:VGMIG. No suitable driver No suitable driver Problem Resolution: Check the following: - Ensure that you updated the Properties for VAGenToEGLMigration to include the location of db2java.zip on the Classpath tab and that you clicked Compute Now on the Classpath tab to complete the update. - Check your system environment variables: - The classpath environment variable must include: sqlInstallationDirectory\SQLLIB\java\db2java.zip - The path environment variable must includes: - sqlInstallationDirectory\SQLLIB\BIN - sqlInstallationDirectory\SQLLIB\FUNCTION Note that this problem can occur when the classpath or path statement is too long, resulting in some of the subdirectories being omitted. If you used the default installation directory "Program Files", try to shorten the path environment variable by using one of the following techniques: - Change the long name for a directory to the short name that Windows recognizes. For example, change "Program Files" (without the quotes) to "Progra~1" (without the quotes). The short name associated with a directory is determined by opening a Windows Command prompt and running the command "DIR /X" command (without the quotes) from the appropriate directory. - Reinstall DB2 using shorter product directory names without blanks (for example, SQLLIB instead of the default "Program Files\SQLLIB"). Alternatively, try one of the following techniques: - Try moving the SQL-related information to the beginning of the classpath and path environment variables. - Try copying the db2jdbc.dll file from the \SQLLIB directory to a directory that is in your path environment variable (for example, to vajavaInstallDirectory\ide\program)
Local fix
Problem summary
Customer does not use -O option and specified an empty plan file in the stage 1 VAGen to EGL migration, then the migration tool throws a NullPointerException.
Problem conclusion
It will be OK to update the VAGen to EGL Migration Guide.
Temporary fix
Comments
APAR Information
APAR number
PM05410
Reported component name
VAGEN2RBD MIGRA
Reported component ID
5724S5002
Reported release
751
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-18
Closed date
2010-04-06
Last modified date
2010-04-06
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSMQ79","label":"Rational Business Developer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
06 April 2010