IBM Support

PM85325: PROBLEMS WHEN CHANGING FROM JAVA6 TO JAVA7

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a customer configures a cell, and then installs Java7 but
    does NOT change the WAS level, then the postinstaller does not
    resynchronize the symlinks in WAS_HOME.
    
    managesdk.sh to change to Java7 fails with
    ADML3000E: The tool is unable to locate the
    systemlaunch.properties file: java.io.IOException: Cannot
    locate systemlaunch.properties at path:
    /WAS_HOME/AppServer/properties/systemlaunch/base/null.systemlaun
    ch.properties
    

Local fix

  • run /WAS_HOME/bin/zUpdateSymlinks.sh to resynchronize the
    symlinks in WAS_HOME
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.0 and V8.5                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Java 7 symlinks not updated when        *
    *                      installing it after a config root has   *
    *                      been created                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a user configures a server on z/OS and then decides
    afterwards
    to install and use Java 7, some metadata required to detect
    that
    Java 7 has been installed is not correct. This can lead to
    symlinks
    not being properly updated and not being able to be used.
    

Problem conclusion

  • A code change was added to fix some of the metadata
    accordingly.
    
    APAR PM85325 is currently targeted for inclusion in
    Fix Packs 8.0.0.7 and 8.5.5.0 of WebSphere Application
    Server V8.5 and V8.0
    
    Another APAR will be created to fix an additional scenario
    which is required to have Java 7 detected properly. This APAR
    will be updated with the new APAR once it is created.
    
    APAR PM92794 has been created to fix the additional scenario
    listed above. That APAR is scheduled to be included into fix
    packs 8.0.0.8 and 8.5.5.1 of WebSphere Application Server V8.0
    and V8.5.
    
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    
    In addition, please refer to URL:
    http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack PTF information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM85325

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-21

  • Closed date

    2013-05-22

  • Last modified date

    2013-07-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

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021