Fixes are available
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21
APAR status
Closed as program error.
Error description
After unjaring the remote migration jar file and running the WASPreUpgrade command, a java not found error is reported.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of Remote Migration Tool for IBM * * WebSphere Application Server v8.5.5 * **************************************************************** * PROBLEM DESCRIPTION: Remote version of WASPreUpgrade tool * * fails with "<path>/java: not found". * **************************************************************** * RECOMMENDATION: * **************************************************************** The createRemoteMigrJar tool only collects the $WAS_HOME/java directory tree. If the command default JDK is set to another java version then the cmdDefaultSDK.properties file becomes inconsistent with the java directory that was collected. Migration supports all JDKs shipped but recommends the ${WAS_INSTALL_ROOT}/java be used.
Problem conclusion
Adjusted the collection tool to discover which JDK the cmdDefaultSDK.properties is pointing to, and adjusted it to point to the default. If the default java is not available then we collect the java version being pointed to by the cmdDefaultSDK.properties file. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM98900
Reported component name
WAS EXPRESS
Reported component ID
5724I6300
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-10-11
Closed date
2013-10-16
Last modified date
2013-10-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WAS EXPRESS
Fixed component ID
5724I6300
Applicable component levels
R850 PSY
UP
Document Information
Modified date:
28 April 2022