Deployment of the software

In most installations, several z/OS® images exist. These images might, for example, separate workloads or isolate development from production. In such environments, it is often desirable to perform the actual software installation process only once and then deploy that software on several images.

To support this method of installing the software once and deploying it on multiple images, in zSecure you can create configuration data sets. These data sets can be used to specify all configuration options for a specific instance of the software in a separate data set. You can also use configuration data sets to specify a new data set name convention for the data sets where the target and distribution libraries are copied during distribution.

You can install a full set of zSecure products and features. After installing, you can use parmlib member IFAPRDxx to specify which products and features are not available on each z/OS image. For example, you might want to disable zSecure Admin and zSecure Audit for RACF® on a z/OS image that uses ACF2 as the security manager.

Distribution-oriented installation is supported between images with unlike licenses, or unlike security managers. For example, if zSecure software has already been installed on a z/OS image for RACF, you can use the same software on another z/OS image even if that image uses a different security manager such as ACF2 or Top Secret. In such cases:

  1. Perform a distribution to the new image.
  2. Create one or more zSecure configuration files to specify the options required to operate zSecure in that environment.
Note: Distribution-oriented installation is not supported between z/OS and z/VM®. If you want to use zSecure on both z/OS and z/VM platforms, you must install the software separately for each platform.