IBM Support

PK40567: INSTALL_IHS COMMAND MAY NOT WORK FOR SYMBOLIC LINKS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • install_ihs command  may not work with symbolic Symlinks.
    customers might have symlinks in the path to the SMP/E read-only
    APPLY directory.  the first component of their path is a symlink
    that apparently changes among members of a sysplex. By default,
    the z/OS shell uses the link target as the result of a built-in
    cd or pwd.
    

Local fix

  • One suggestion fis to provide the product path to the
    install_ihs shell.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM HTTP Server for WebSphere   *
    *   (powered by Apache) on z/OS                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: IHS install is using the physical path  *
    *                      when creating symlinks from the         *
    *                      installation directory to the product   *
    *                      directory. If symbolic links are used   *
    *                      anywhere within the IHS product         *
    *                      directory, when the symlink is changed  *
    *                      to point to a different mount point for *
    *                      the product directory the installed     *
    *                      product does not reflect the change.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Path references within the IHS product directory are set at
    install time by the install_ihs script. The script creates
    symlinks for some files from the install directory to the
    product directory. If the product directory itself has
    symlinks then the symlink from the install directory should
    have the logical path, but instead it has the physical path
    to the product directory.
    

Problem conclusion

  • If using a symlink in the product directory path, the symbolic
    link will be used by the product installation, not the physical
    path. Users can then change the mount point of where the product
    directory is, along with the symbolic link from the installation
    directory to it. The path in the install directory will be
    updated when the symlink is changed, there will no longer be
    references to the physical mount point.
    
    The symlink will only be obtained if the product directory is
    the default path of: /usr/lpp/zWebSphere_OM/V6R1/HTTP/Server.
    If not using the default product directory it is recommended to
    invoke install_ihs using it absolute path.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK40567

  • Reported component name

    WAS IHS ZOS

  • Reported component ID

    5655I3510

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2007-03-05

  • Closed date

    2007-05-30

  • Last modified date

    2007-08-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PK46546

Fix information

  • Fixed component name

    WAS IHS ZOS

  • Fixed component ID

    5655I3510

Applicable component levels

  • R038 PSN

       UP

  • R610 PSN UK25662

       UP07/07/04 P F707

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1"}]

Document Information

Modified date:
09 March 2021