Fix (APAR): PK62917 Status: Fix Release: 6.1.0.15,6.1.0.13,6.1.0.11 Operating System: i5/OS,OS/400 Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 18560 Date: 2008-03-21 Abstract: This problem involves fixing the setupCmdLine scripts for a 6.1 WebSphere Application Client install. This includes the product level setupCmdLine and the setupCmdLine scripts t Description/symptom of problem: PK62917 resolves the following problem: ERROR DESCRIPTION: This problem involves fixing the setupCmdLine scripts for a 6.1 WebSphere Application Client install. This includes the product level setupCmdLine and the setupCmdLine scripts that exist in the bin directory of each profile. System i is unique in that it supports the use of three JVMs. Classic (Sun 64bit), IBM Technology for Java Virtual Machine - 32bit, and IBM Technology for Java Virtual Machine - 64 bit. These three are shipped with i5/OS. The problem occurs when the product is configured to use one of the IBM Technology flavors, and a profile is configured to use Classic. The setupCmdLine files (for 6.1) only export JAVA_HOME if the product is not configured to use Classic. When the product setupCmdLine uses IBM Technology for Java Virtual Machine, (its INSTANCE_USE_J9 value is 'true') it exports JAVA_HOME as the path to the IBM Technology for Java Virtual Machine (32bit or 64bit) JDK. It then sets variables for IBM Technology for Java Virtual Machine usage before calling the profile setupCmdLine script. The profile is set to use Classic, does not export JAVA_HOME, but overrides the settings done by the product's setupCmdLine script. This is fine and is expected. However, it does export INSTANCE_USE_J9=false and leaves JAVA_HOME to point to the IBM Technology for Java Virtual Machine JDK product. When it returns to the place in the products setupCmdLine where it was called we have a messed-up set of configuration variables: part Classic and part IBM Technology for Java Virtual Machine. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: i5/OS usere of IBM WebSphere Application Client V6.1 who have the product configured to use IBM Technology for Java Virtual Machine (32bit or 64bit), and have a profile configured to use Classic. PROBLEM DESCRIPTION: This problem involves fixing the setupCmdLine scripts for a 6.1 WebSphere Application Client install. This includes the product level setupCmdLine and the setupCmdLine scripts that exist in the bin directory of each profile. RECOMMENDATION: None This problem involves fixing the setupCmdLine scripts for a V6.1 WebSphere Application Client install. This includes the product level setupCmdLine and the setupCmdLine scripts that exist in the bin directory of each profile. The problem occurs when the product is configured to use one of the IBM Technology flavors, and a profile is configured to use Classic. The setupCmdLine files (for 6.1) only export JAVA_HOME if the product is not configured to use Classic. When the product setupCmdLine uses IBM Technology for Java Virtual Machine, (its INSTANCE_USE_J9 value is 'true') it exports JAVA_HOME as the path to the IBM Technology for Java Virtual Machine (32bit or 64bit) JDK. It then sets variables for IBM Technology for Java Virtual Machine usage before calling the profile setupCmdLine script. The profile is set to use Classic, does not export JAVA_HOME, but overrides the settings done by the product's setupCmdLine script. This is fine and is expected. However, it does export INSTANCE_USE_J9=false and leaves JAVA_HOME to point to the IBM Technology for Java Virtual Machine JDK product. When it returns to the place in the products setupCmdLine where it was called we have a messed-up set of configuration variables: part Classic and part IBM Technology for Java Virtual Machine. PROBLEM CONCLUSION: This APAR (interim Fix) will fix all existing profiles and allow new profiles to create correctly. This is the same fix as PK62486 for the WesSphere Application Server V6.1 install. The fix for PK62486 is currently targeted for inclusion in fix pack 6.1.0.17. Please refer to the recommended updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 Directions to apply fix: This fix applies to WebSphere Application Client 6.1 on i5/OS, versions 6.1.0.11, 6.1.0.13 and 6.1.0.15. Install the Update Installer for i5/OS, which can be downloaded here: http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg24012718 = The Update Installer install location, default is /QIBM/ProdData/WebSphere/UpdateInstaller/V61/UPDI = WebSphere Application Client install location, an example is /QIBM/ProdData/WebSphere/AppClient/V61/client 1. Copy 6.1.0.15-WS-AppClient-IFPK62917.pak file to /maintenance 2. End all servers assoicated with the WebSphere install. 3. From Qshell a. cd b. update -W product.location= -W maintenance.package=/maintenance/6.1.0.15-WS-AppClient-IFPK62917.pak Directions to remove fix: 1. End all servers associated with the WebSphere install. 2. From Qshell a. cd b. update -W product.location= -W backup.package=6.1.0.15-WS-AppClient-IFPK62917.pak -W update.type=uninstall Directions to re-apply fix: Follow the Fix instructions to apply the fix. Additional Information: