IBM Support

PI73481: IN IDZ V14.0.0.3 AND IBM Z/OS EXPLORER V3.0, RSE SEVER CANNOT START WHEN PATH TO RSE IS A SYMBOLIC LINK

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In IBM z/OS Explorer v3 host, if the path to RSE server is a
    symbolic link, the server cannot start. For example if the
    actual path is /$VERSION/usr/lpp/IBM/zexpl, and is referenced as
    /usr/lpp/IBM/zexpl, server startup will fail with the following
    message:
    
    ERROR -- changing RSE_HOME is not supported
    
    The same issue can be reproduced in IBM Developer for z Systems
    v14 host and IBM Rational Developer for z Systems v9.5.1 host,
    as both have  IBM Explorer for z/OS v3 host as a prerequisite.
    

Local fix

  • Specify the full path of RSE_HOME in /etc/zexpl/rse.env. For
    example:
    RSE_HOME=/$VERSION/usr/lpp/IBM/zexpl
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: 01.z/OS system programmer                    *
    *                 02.All z/OS Explorer users creating z/OS     *
    *                    UNIX files/directories.                   *
    *                 03.z/OS System programmer                    *
    *                 04.Users of z/OS Explorer, RDz, or IDz who   *
    *                    enable SSL/TLS.                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: 01.RSED will not start with symbolic    *
    *                         link in path                         *
    *                      02.Enhancement to set a umask value,    *
    *                         which controls the default access    *
    *                         permission mask for files and        *
    *                         directories created via z/OS         *
    *                         Explorer.                            *
    *                      03.Enhancements to improve FEKLOGS,     *
    *                         the log collection tool.             *
    *                      04.Enhancement to enable TLSv1.1 and    *
    *                         TLSv1.2 by default, on top of the    *
    *                         existing TLSv1.0.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    01.RSED will not start with symbolic link in path (variables
       RSE_HOME or RSE_CFG) and ends with ERROR -- changing
       RSE_HOME is not supported
    02.Enhancement to set a umask value, which controls the default
       access permission mask for files and directories created via
       z/OS Explorer. New environment varialbe _RSE_UMASK is added
       to rse.env. See the variable documentation for more
       information. default: _RSE_UMASK=RWX.N.N
    03.Enhancements to improve FEKLOGS, the log collection tool.
    04.Enhancement to enable TLSv1.1 and TLSv1.2 by default, on top
       of the existing TLSv1.0. Now, no host changes are required
       to support these protocols when a client connects,
       regardless of the client's set of acceptable protocols.
    

Problem conclusion

  • 01.code is updated to expand symbolic links before validating
       startup args against rse.env definitions
    02.Enhancement to set a umask value, which controls the default
       access permission mask for files and directories created via
       z/OS Explorer. New environment varialbe _RSE_UMASK is added
       to rse.env. See the variable documentation for more
       information. default: _RSE_UMASK=RWX.N.N
    03.Enhancements to improve FEKLOGS, the log collection tool.
    04.RSE now enables all current TLS protocols, so that the
       highest version in common between client and host will be
       the new default. When not updated, this is TLSv1.2 for v3015
       (Jan 2017) and higher clients, and TLSv1.0 for older
       clients.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI73481

  • Reported component name

    EXP FOR Z/OS HO

  • Reported component ID

    5655EXP23

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-08

  • Closed date

    2017-01-19

  • Last modified date

    2017-03-02

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

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

    UI44105

Modules/Macros

  •    FEKFDST0 FEKFENVP FEKFENVR FEKFENVS FEKFLOGS
    FEKFRSES FEKLOGR  FEKSENV
    

Fix information

  • Fixed component name

    EXP FOR Z/OS HO

  • Fixed component ID

    5655EXP23

Applicable component levels

  • R300 PSY UI44105

       UP17/02/15 P F702

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.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSBDYH","label":"IBM Explorer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 March 2017