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.

Hardware prerequisites

z15™
z14®/z14 Model ZR1
z13®/z13s®
zEnterprise® EC12/BC12

Software prerequisites

z/OS® UNIX System Services enabled on any of following operating systems:
- z/OS V2R4 with all the following PTFs installed:
  - UI64830
  - UI64837
  - UI64839
  - UI64940
  - UI65567
- z/OS V2R3 with all the following PTFs installed:
  - UI61308
  - UI61375
  - UI61747
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).

Notes:

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.

Configuration

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/env exists. If not configured, refer to the instructions in Verifying the env command path.
Ensure that /tmp has at least 1 GB or more of disk space configured. To use an alternative file system, you can set the TMPDIR environment variable to a directory that has sufficient space.

Environment variables

You need to setup environment variables before using IBM SDK for Node.js - z/OS.

Run setup.sh to 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. Run the .nodeenv script generated by setup.sh to set the required environment variables in the current shell using the dot command (.):
```
$ . <nodejs_dir>/.nodeenv
```
This command also adds <nodejs_dir>/bin to your PATH, where the node binary is located.

npm configuration

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 npm option. For example:
```
npm install <npm_module> --unsafe-perm
```
You can configure this option as default with:
```
npm config set unsafe-perm true
```
Create a user id: nobody and ensure it is a member of a group. npm switches to this nobody uid/gid as necessary when running as BPXROOT.