PQ65263: JAVA_HOME NOT FOUND WHEN MIGRATING FROM 3.5 TO 4.0 ON WAS FOR LINUX FOR 390.

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
Customer attempts to migrate websphere 3.5 to 4.0 and fails
with JAVA_HOME is not found. In the log error MIGR0257E:
Environment variable JAVA_HOME was not set is generated.
Local fix
The problem is the call to version 3.5 XMLConfig is failing.
When migration calls version 3.5 XMLConfig, the 122 jdk that
is installed with WebSphere 3.5 is used to run
XMLConfig.  Therefore the 122 jdk JAVA_HOME is not
being found.  The migration code looks for the jdk122
in one of three locations: $ WAS_HOME/IBMJavaLink,
/opt/IBMJava2-122 or $ WAS_HOME/IBMJava2-122, where
WAS_HOME is the 3.5 WAS_HOME.  IF the 122 jdk is
not installed in one of those 3 locations the call to
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 that migrate from WebSphere v3.5.x           *
*                 to v4.0.x on Linux for 390.                  *
****************************************************************
* PROBLEM DESCRIPTION: The 122 jdk JAVA_HOME was not found     *
*                      when attempting to call XMLConfig       *
*                      from WASPreUpgrade.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When attempting to run WASPreUpgrade the error MIGR0257E:
Environment variable JAVA_HOME was not set was generated.
The problem is the call to the v3.5.x XMLConfig failed.
When migration calls v3.5.x XMLConfig, the 122 jdk that is
installed with v3.5.x is used to run XMLConfig.  Therefore
the 122 jdk JAVA_HOME was not found.  The migration
code looks for the jdk122 in one of three locations:
$WAS_HOME/IBMJavaLink, /opt/IBMJava2-122 or
$WAS_HOME/IBMJava2-122, where WAS_HOME is the v3.5.x WAS_HOME.
If the 122 jdk is not installed in one of those 3 locations
the call to XMLConfig fails.
Problem conclusion
Additional checking was added to look for the 122 jdk JAVA_HOME
in the following two locations when running WebSphere on Linux
for 390: /opt/IBMJava2-s390-13 or $WAS_HOME/IBMJava2-s390-13,
where WAS_HOME is the v3.5x WAS_HOME.
Temporary fix
With the workaround provided to the customer, they were
able to proceed.  Waiting to hear back from the customer to
find out if they will be testing the actual code fix.
The customer will be back in the office on August 26th.
Never heard back from Level2 about whether or not the
customer will test the fix.  Therefore, since the
fix was unit tested the apar is being closed
Comments
APAR information
APAR number PQ65263
Reported component name WAS AE LINUX/ZS
Reported component ID 5724B6108
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-14
Closed date 2002-08-29
Last modified date 2002-08-29

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
MIGRATE          

SRLS

Fix information
Fixed component name WAS AE LINUX/ZS
Fixed component ID 5724B6108

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65263
IBM Group: Software Group
Modified date: Aug 29, 2002