IBM Support

PI59309: UPDATESYMLINKS.SH SCRIPT MAY NOT REPORT AN ERROR IF A DIRECTORY EXISTS WHEN IT TRIES TO CERATE A SYMBOLIC LINK

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • zUpdateSymlinks.sh may be ran manually or part of
    another script - applyPTF.sh or runConfigActions.sh.
    
    If there is an existing directory already there with the same
    name as the symlink the script is trying to create, the sybolic
    link may not be created, but it would still report a success in
    the output log:
    
    CWLCS0710I Symbolic link created:
    /WebSphere/ND/AppServer/java_1.7.1_31
    
    The script will be updated with extra checks so a failure is
    reported in this situation.
    

Local fix

  • Create the symbolic link manually:
    
    ln -s /target/directory/or/file .
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V8.5                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Incorrect java directory structure in   *
    *                      the  configuration image is not         *
    *                      reported by script zUpdateSymlinks.sh   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The customer installed Java 1.7.1 for their WebSphere
    Application Server V8.5 at Fix Pack Level 8.5.5.8, but once
    they
    switched the server to use it, the server failed with:
    BBOO0335E BPX1LOD LOAD OF libjvm.so FAILED RC=00000081,
    REASON=0594003D.
    The failure was caused by incorrectly built symbolic links.
    The main java directory for 1.7.1 was not a symlink to install
    hfs, but actually a directory.
    zUpdateSymlinks.sh is invoked during the upgrade to the new Fix
    Pack level. zUpdateSymlinks.sh will create symlinks for
    installed java directories if they do not alreadys exit in the
    configuration hfs. If a java directory already exists it will
    be
    skipped over and assumed to be correctly linked.
    Support is needed such that if a java directory exists in the
    configuration hfs that it is a symbolic link back to its
    corresponding java directory with in the installation hfs.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI59309

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-03-17

  • Closed date

    2016-04-04

  • Last modified date

    2016-04-04

  • 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:
28 April 2022