Customization setup

z/OS® Explorer contains several sample configuration files and sample JCL. To avoid overwriting your customizations when applying maintenance, copy all of these members and z/OS UNIX files to a different location, and customize the copy.

Some functions of z/OS Explorer require the existence of certain directories in z/OS UNIX, which must be created during the customization of the product. To ease the installation effort, a sample job, FEKSETUP, is provided to create the copies and the required directories.

Note: The Host Configuration Utility Guide (SC27-8436) describes the host system configuration when using the Host Configuration utility. The FEKSETUP job and the utility do some of the same tasks, with no way of checking if those tasks have already been performed. Therefore, it is possible to undo changes that have already been made. For this reason, do not use both methods for a single installation.

To create customizable copies of configuration files and configuration JCL, and to create required z/OS UNIX directories, customize and submit the sample FEKSETUP member in the FEK.SFEKSAMP data set. The required customization steps are described within the member.

This job performs the following tasks:
  • Create FEK.#CUST.PARMLIB and populate it with sample configuration files.
  • Create FEK.#CUST.PROCLIB and populate it with sample SYS1.PROCLIB members.
  • Create FEK.#CUST.JCL and populate it with sample configuration JCL.
  • Create FEK.#CUST.CNTL and populate it with sample server startup scripts.
  • Create /etc/zexpl/* and populate it with sample configuration files.
  • Create /var/zexpl/* as work directories for various z/OS Explorer functions, and populate it with sample files.
Note:
  • The configuration steps in this publication use the member and file locations created by the FEKSETUP job, unless noted otherwise. The original samples, which should not be updated, are in FEK.SFEKSAMP and /usr/lpp/IBM/zexpl/samples/.
  • For more details on which sample members are copied to which data set, and for more details on which directories are created, their permission bitmask, and where the various sample files are copied to, see the comments in FEK.SFEKSAMP(FEKSETUP).
  • To aid in migrating an existing setup, the comments in FEK.SFEKSAMP(FEKSETUP) also document the changes between different versions of z/OS Explorer.
  • If you want to keep all of the z/OS Explorer z/OS UNIX files in the same file system (HFS or zFS), but also want the configuration files placed in /etc/zexpl, you can use symbolic links to solve this problem. The following sample z/OS UNIX commands create a new directory in the existing file system (/usr/lpp/IBM/zexpl/cust) and define a symbolic link (/etc/zexpl) to it: 
    					mkdir /usr/lpp/IBM/zexpl/cust
					ln –s /usr/lpp/IBM/zexpl/cust /etc/zexpl