Setting up integrations to interact with z/OS

You can use IBM Z® Open Editor on your computer without any connection to z/OS® system and download files manually by using an FTP command or similar method. However, you can augment the capabilities of IBM Z Open Editor and enjoy a seamless integration of z/OS with IBM® Remote System Explorer API (RSE API) or the Zowe™ open source project. The Zowe project provides great tools that work perfectly with the IBM Z Open Editor.

When using IBM Z Open Editor, you can choose how to interact with z/OS with regard to the following aspects:

  • Use RSE API or the Zowe default z/OSMF as the host component

  • Use the command line or graphical interface to interact with z/OS

Next, you can use the following client-side tools based on your decision:

Available host component To use command line, install... To use graphical interface, install...
RSE API
  • Zowe CLI, and
  • IBM RSE API Plug-in for Zowe CLI
Zowe Explorer
z/OSMF Zowe CLI Zowe Explorer

Detailed information about these tools is as follows:

Installing Zowe CLI

The prerequisites for installing Zowe CLI are as follows:

  • Client: Install Node.js version 10, or a later version

  • Host (select one or both):

    • Configure z/OSMF if you plan to use Zowe CLI without RSE CLI plug-in

    • Install and configure IBM Remote System Explorer API if you plan to use Zowe CLI along with RSE CLI plug-in to extend Zowe CLI

You can install Zowe CLI using one of the methods below:

  • Follow the Zowe documentation on Installing Zowe CLI to install Zowe CLI from the Zowe.org website or the npmjs.com npm package registry.

  • Alternatively, you can get a certified IBM Zowe distribution from IBM Mainframe DEV. You can also purchase technical support for Zowe from IBM for this distribution.

Warning:

IBM recommends installing Secure Credential Store Plug-in for Zowe CLI to encrypt the credentials stored in your Zowe CLI profiles. For more information, see npm.

Installing IBM RSE API Plug-in for Zowe CLI

Prerequisites

Before installing IBM RSE API Plug-in for Zowe CLI on your development machine, you must install Zowe CLI 6.13 or later. For more information about installing Zowe CLI, see Installing Zowe CLI.

Installing the requisite IBM RSE API z/OS host component

Confirm with your system administrator that the following host components are installed and configured on the z/OS host system:

  • The host component of z/OS Explorer 3.1.1 or 3.2, which is the prerequisite of the RSE API host component.

  • The RSE API host component, which provides a collection of REST APIs that allow a client to work with various components on the z/OS host system, including MVS data sets, z/OS UNIX files and commands, JES jobs, and more.

Note: Even if your system administrator has previously installed RSE on your z/OS, an update is needed to get the capabilities described here.

For information about installing and configuring the RSE API host component, see RSE API documentation.

Installing the IBM RSE API Plug-in for Zowe CLI

After installing and configuring the prerequisites and the host component, follow these steps to install the RSE CLI plug-in. You can choose to download the plug-in from IBM as a code-signed archive file to install locally, or do an online installation from the public repository at npmjs.com, which is the repository from which you installed Zowe CLI itself.

Option 1: Download install package from IBM

  1. Navigate to the Mainframe DEV website at https://ibm.github.io/mainframe-downloads/downloads.html.

  2. Click More info on the IBM Wazi Developer for Red Hat CodeReady Workspaces tab.

  3. In the Code row, click VSCode.

  4. You are then redirected to the Software License Agreement page. Review the License Agreement and click I Agree. You will be prompted to save or open a compressed .zip file in your browser.

  5. Save the compressed .zip file to your workstation.

  6. Extract the compressed .zip file on your workstation. You will find various files in the archive including the Z Open Editor archive as well as a file named ibm-rse-api-for-zowe-cli-v.r.m.tgz.

  7. Optionally, follow the instructions in the included README.txt file to verify the code signature to ensure the file was signed against a trusted IBM certificate.

  8. Install the RSE CLI plug-in by entering the following command in the terminal:

    zowe plugins install path/to/download/ibm-rse-api-for-zowe-cli-v.r.m.tgz

    where path/to/download/ibm-rse-api-for-zowe-cli-v.r.m.tgz should be defined with your own file path.

Option 2: Install from npmjs.com

  1. Install the RSE CLI plug-in by entering the following command in the terminal:

    zowe plugins install @ibm/rse-api-for-zowe-cli

Validating installation

If the installation was successful, you can see the following message printed in the terminal:

Installed plugin name = '@ibm/ibm-rse-api-for-zowe-cli'

_____ Validation results for plugin '@ibm/ibm-rse-api-for-zowe-cli' _____
This plugin was successfully validated. Enjoy the plugin.

Getting help

After installing the RSE CLI plug-in, you can see all the command options of the plug-in by entering the command zowe rse --help into the terminal.

Updating the IBM RSE API Plug-in for Zowe CLI

When a new version of the RSE API Plug-in for Zowe CLI is released, you might not only need to install the latest version of the binaries, but might also need to migrate the configuration and profiles of each user account because some settings might have changed and the Zowe CLI framework currently does not support an automated migration process.

For example, in RSE CLI plug-in 1.1.0, basepath and protocol were stored securely in your profile files via the Zowe Secure Credential Store (SCS). With the release of RSE CLI plug-in 1.1.1, we have changed those to be stored in plain text as a convenience update for Mac users to reduce the number of prompts when accessing the Mac Keychain, which requires changes to the profile files. However, enabling this requires applying updates to the individual folders that store Zowe CLI profiles, which are described in detail further below.

Finally, RSE CLI plug-in 1.1.1 also offers the choice of not storing username and password in the Zowe CLI profile files at all, instead using the interactive zowe auth command. Again, for proper support of this new capability, migrate to the newest versions available and update their profile files.

Note: If you do not plan to use any of these new capabilities (no storage of username/password, less prompting on Macs), no migration is required. You can choose to continue using RSE API Plug-in for Zowe CLI 1.1.0, or migrate to the new binaries to version 1.1.1 without migrating your profile files. If you do want to use any of these new features, follow all the instructions below.

Getting started with the update

If you are using Zowe Secure Credential Store (SCS), follow the following steps to revert your secure Zowe profiles to plain-text profiles before updating RSE CLI plug-in. This will help ensure that you can continue using your existing Zowe profiles after updating. The instructions for updating RSE CLI plug-in include a step for re-securing your Zowe profiles after the update process is complete.

  1. Check your version of Zowe SCS with the command zowe plugins list

  2. If the version number is below 4.1.0, run the following command to update Zowe SCS:

    zowe plugins update @zowe/secure-credential-store-for-zowe-cli@zowe-v1-lts
  3. Revert Zowe profile files back to plain text with the command zowe scs revert -f

Update previous npmjs.com install

If the previous installation of the RSE CLI plug-in was from npmjs.com, run the following command to update to the latest version available on npmjs.com:

zowe plugins update @ibm/rse-api-for-zowe-cli

Update previous .tgz install

  1. Uninstall the older version of RSE CLI plug-in:

    • If the original .tgz file of the older version is still in the original location from the installation, run the following command.

      zowe plugins uninstall @ibm/rse-api-for-zowe-cli
    • If the original .tgz file is no longer in the original location from the installation, complete the following procedure:

      1. Use the file explorer to open the .zowe folder in the home directory.

      2. Within the .zowe directory, go to the plugins/installed/node_modules/@ibm directory and delete the rse-api-for-zowe-cli folder.

      3. Navigate to the .zowe/plugins directory, open the plugins.json file in edit mode and remove the @ibm/rse-api-for-zowe-cli section as shown below and save the file.

        "@ibm/rse-api-for-zowe-cli": {
          "package": "@ibm/rse-api-for-zowe-cli",
          "registry": "installation/location",
          "version": "1.0.0"
        }
  2. Verify the uninstallation.

    Run the command zowe plugins list. The list of plug-ins should no longer contain @ibm/rse-api-for-zowe-cli upon a successful uninstallation.

  3. Delete rse_meta.yaml file from the .zowe/profiles/rse directory.

  4. Install the new version of RSE CLI plug-in.

    Refer back to Installing the IBM RSE API Plug-in for Zowe CLI to install the new .tgz download of IBM RSE API Plug-in for Zowe CLI.

  5. If using Zowe Secure Credential Store, run the command zowe scs update to store username and password securely.

  6. If you have existing RSE profiles for Zowe, run the command zowe profiles set-default rse <profileName>, where <profileName> is the name of the profile you want to set as the default RSE profile.

Moving from .tgz install to npmjs.com install

  1. Follow step 1 - 3 of Update previous .tgz install.

  2. Run command zowe plugins install @ibm/rse-api-for-zowe-cli, which will pull from npmjs.com.

Setting log levels for IBM RSE CLI plug-in

Setting up log levels for the RSE CLI plug-in follows the same method used to set Zowe CLI log levels, and logs are written to the log file location /.zowe/zowe/logs/zowe.log. You can set the log level to adjust the level of detail that is written to the log file.

Important! Setting the log level to TRACE or ALL may result in "sensitive" data being logged.

Environment Variable Description Values Default
ZOWE_APP_LOG_LEVEL Zowe CLI and RSE CLI plug-in logging level Log4JS log levels (OFF, TRACE, DEBUG, INFO, WARN, ERROR, FATAL) DEBUG

Single sign-on support for IBM RSE CLI plug-in

RSE CLI plug-in has single sign-on (SSO) support using JSON Web Tokens (JWT) that are issued by the RSE API host component to the RSE profile. If the RSE API host component is configured and registered with the Zowe API Mediation Layer (API ML), the RSE CLI plug-in also supports SSO using a JWT that is issued to a Zowe CLI base profile by the API ML. The JWTs can be used for authentication with the RSE API host component via command line operations as well as operations done within IBM Z Open Editor and Zowe Explorer's z/OS integrations.

If any issues or concerns arise during installation or while working with RSE CLI plug-in, refer to the known issues documentation with the RSE CLI plug-in here.