Installing and configuring the SMP/E edition
The Program Directory for the product details specific installation requirements and instructions in Chapter 5 and Chapter 6. For information about the latest APAR fixes, see Fix list for IBM SDK for Node.js - z/OS.
The following checklist summarizes the key configuration steps for a successful installation.
- z14®/z14 Model ZR1
- zEnterprise® EC12/BC12
- z/OS® UNIX System Services enabled on any of following operating systems:
- Integrated Cryptographic Services Facility (ICSF) must be enabled on systems where IBM® SDK for Node.js - z/OS is run. For details, refer to ICSF System Programmer's Guide (SC14-7507) and ICSF Administrator's Guide (SC14-7506).
- Python 3.8.2 or later 3.x versions, required to compile native add-ons. It must also be defined in your PATH environment variable.
- Make 4.1 or later, required to compile native add-ons. It must also be defined in your PATH environment variable..
- SCRT 28.1.0 or above is required to generate sub-capacity reports to report IBM SDK for Node.js - z/OS 14.0 metrics with the Sub-Capacity Reporting Tool (SCRT).
- To obtain IBM Open Enterprise Python for z/OS, visit IBM Open Enterprise Python for z/OS product page.
- To obtain Make, visit the Make for z/OS download page.
- If you use the bash shell, make sure you use Rocket bash because the default bash shell that ships with the operating system is known to have auto-conversion issues. The Rocket bash is available for download at Bash for z/OS on the Rocket website.
IBM SDK for Node.js - z/OS is an OMVS-based application, which requires certain configuration on the z/OS UNIX System Services file system to ensure proper operation.
- Validate that
/usr/bin/envexists. If not configured, refer to the instructions in Verifying the env command path.
- Ensure that
/tmphas at least 1 GB or more of disk space configured. To use an alternative file system, you can set the
TMPDIRenvironment variable to a directory that has sufficient space.
setup.shto validate system prerequisites, setup environment variables, and optionally install the njsc C/C++ compiler:
$ cd <nodejs_dir> $ ./setup.sh
- In order for Node.js to operate correctly, specific environment variables must be set.
.nodeenvscript generated by
setup.shto set the required environment variables in the current shell using the dot command (.):
This command also adds <nodejs_dir>/bin to your PATH, where the
$ . <nodejs_dir>/.nodeenv
nodebinary is located.
The npm utility is included in IBM SDK for Node.js - z/OS to install Node.js modules and packages. The npm utility performs checks to limit unsafe installation of modules by root / BPXROOT. To proceed to use BPXROOT id, you can take either of the following steps:
- Run with the --unsafe-perm
option. For example:
You can configure this option as default with:
npm install <npm_module> --unsafe-perm
npm config set unsafe-perm true
- Create a user id:
nobodyand ensure it is a member of a group. npm switches to this
nobodyuid/gid as necessary when running as BPXROOT.