IBM Support

PH69974: INSTALLATION SCRIPT SETUP.SH FAILS WHEN RUN ON READ-ONLY FILESYSTEM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After the base installation of Node.js for z/OS, the final
    installation step of running the setup.sh script fails when run
    on a filesystem that is read-only.  The setup.sh script attempts
    to generate the .env environment variable script in the Node.js
    installation location, which fails if the location is read-only.
    

Local fix

  • Users may manually export the .env environment variables as a
    workaround:
    
    export _BPXK_AUTOCVT=ON
    export _CEE_RUNOPTS="$_CEE_RUNOPTS FILETAG(AUTOCVT,AUTOTAG)
    POSIX(ON)"
    export _TAG_REDIR_IN=txt
    export _TAG_REDIR_ERR=txt
    export _TAG_REDIR_OUT=txt
    export PATH="/path/to/node/install/bin:$PATH"
    export npm_config_nodedir="/path/to/node/install"
    export npm_config_zoslib_include_dir="/path/to/node/install/inc
    lude/node/zoslib"
    export CC=clang
    export CXX=clang++
    export LINK=$CXX
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Open Enterprise SDK for *
    *                 Node.js 22.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: This PTF enhances the setup.sh script   *
    *                      to support specifying a custom output   *
    *                      directory for the generated .env file   *
    *                      and setup log.                          *
    ****************************************************************
    * RECOMMENDATION: Apply provided service                       *
    ****************************************************************
    This PTF enhances the setup.sh script to support specifying a
    custom output directory for the generated .env file and setup
    log. Users can now pass a writable directory path as the first
    argument when running setup.sh to work around read-only
    filesystem restrictions.
    

Problem conclusion

  • IBM is releasing a cumulative update to the IBM Open Enterprise
    SDK for Node.js 22.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH69974

  • Reported component name

    SDK FOR NODE.JS

  • Reported component ID

    5655NDE00

  • Reported release

    M00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2026-02-03

  • Closed date

    2026-03-26

  • Last modified date

    2026-04-02

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

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

    PH70736

Modules/Macros

  • CNJPHPAX CNJSNPAX
    

Fix information

  • Fixed component name

    SDK FOR NODE.JS

  • Fixed component ID

    5655NDE00

Applicable component levels

  • RM00 PSY UO07278

       UP26/03/31 P F603

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":"BU048","label":"IBM Software"},"Product":{"code":"SSTRRS","label":"IBM SDK for Node.js - z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"M00","Line of Business":{"code":"LOB70","label":"Z TPS"}}]

Document Information

Modified date:
02 April 2026