Predeployment considerations

RSE API supports the cloning of an installation to a different system, thus avoiding the need for a SMP/E installation on each system.

The following data sets, directories, and files are mandatory for deployment to other systems. If you copied a file to a different location, this file must replace its counterpart in the following lists.
Note: The following list does not cover the deployment needs of the prerequisite and co-requisite software.
  • HUH.#CUST.PROCLIB(*)
  • /usr/lpp/IBM/rseapi/*
  • /etc/zexpl/*
  • /var/zexpl/rseapi/* (directory structure only)
Note:
  • HUH and /usr/lpp/IBM/rseapi are the high-level qualifier and path used during the installation of RSE API. HUH.#CUST, /etc/zexpl and /var/zexpl/rseapi are the default locations used during the customization of the product (see Customization setup for more information).
  • You should install RSE API in a private file system (HFS or zFS) to ease the deploying of the z/OS® UNIX parts of the product. If you cannot use a private file system, use an archiving tool such as the z/OS UNIX tar command to transport the z/OS UNIX directories from one system to another. This method is for preserving the attributes (such as program control) for the RSE API files and directories.
    For more information about the following sample commands to archive and restore the RSE API installation directory, see UNIX System Services Command Reference (SA22-7802).
    • Archive: cd /SYS1/usr/lpp/IBM/rseapi; tar -cSf /u/userid/rseapi.tar
    • Restore: cd /SYS2/usr/lpp/IBM/rseapi; tar -xSpf /u/userid/rseapi.tar