Different rse.env

For example we have a local development team, and a remote team who must use encrypted communication and who are not allowed to save their host password on the client. The different encrypted communication settings can be configured using the previous method, but there is a functional change in rse.env (DENY_PASSWORD_SAVE=true), which requires us to use the following method.

In this example, the current RSE daemon setup can be cloned, after which the cloned setup can be updated. Next the RSE daemon startup JCL can be cloned and customized with a new TCP/IP port and the location of the updated configuration files. The MVS customizations (JES Job Monitor, and so on) can be shared between the encrypted and non-encrypted instances. This would result in the following actions:

$ cd /etc/zexpl
$ mkdir /etc/zexpl/secure
$ cp rse.env /etc/zexpl/secure
$ cp ssl.properties /etc/zexpl/secure
$ ls /etc/zexpl/secure/
rse.env    ssl.properties
$ oedit /etc/zexpl/secure/rse.env
      -> change: _RSE_RSED_PORT=4047
      -> change: –Ddaemon.log=/var/zexpl/logs/secure
      -> change: –Duser.log=/var/zexpl/logs/secure
      -> uncomment: –DDENY_PASSWORD_SAVE=true
      -> add at the END:
         # -- NEEDED TO FIND THE REMAINING CONFIGURATION FILES IN CFG_BASE
         CFG_BASE=/etc/zexpl
         CLASSPATH=.:$CFG_BASE:$CLASSPATH
         # -- 
$ oedit /etc/zexpl/secure/ssl.properties
      -> change: change as needed

The commands in the preceding example copy the z/OS® Explorer configuration files that require changes to a newly created secure directory. The daemon.log and user.log variables in rse.env must be updated to define a new log location (which is created automatically if it does not exist). The CLASSPATH update ensures that RSE can find the configuration files that were not copied to the new configuration directory. The ssl.properties file itself can be updated to match your needs.

What is left now is creating a new started task for RSE that uses a new port number and the new /etc/zexpl/secure configuration files.

Refer to the related sections in the IBM® Explorer for z/OS Host Configuration Guide (SC27-8437) for more information on the actions shown previously in this section.