z/OS UNIX directory structure

Figure 1. z/OS UNIX directory structure
z/OS Unix directory structure

Figure 1 shows an overview of the z/OS® UNIX directories used by Developer for z/OS. The following list describes each directory touched by Developer for z/OS, how the location can be changed, and who maintains the data within.

  • /usr/lpp/IBM/zee/ is the root path for the Developer for z/OS product code. The actual location is specified in the zee.env configuration file (variable FEL_HOME). The files within are maintained by SMP/E.
  • Developer for z/OS places files in /usr/lpp/IBM/zexpl/bin, the binaries directory of z/OS Explorer. The actual location is specified in the z/OS Explorer configuration. The files within are maintained by SMP/E.
  • /etc/zexpl/ holds the z/OS Explorer and Developer for z/OS configuration files. The actual location is specified in the RSED started task (variable CNFG). The files within are maintained by the system programmer.
  • /tmp/ is used by Legacy ISPF Gateway to store temporary data. Some IVPs store their output here. The files within are maintained by ISPF and the IVPs. The location can be customized with the TMPDIR variable in rse.env. It is also the default location for Java™ dump files, which can be customized with the _CEE_DUMPTARG variable in rse.env.
    Note: /tmp/ requires permission bit mask 777 to allow each client to create temporary files.
  • /var/zexpl/WORKAREA/ is used by Legacy ISPF Gateway to transfer data between z/OS UNIX and MVS based address spaces. The actual location is specified in rse.env (variable CGI_ISPWORK). The files within are maintained by ISPF.
    Note: /var/zexpl/WORKAREA/ requires permission bit mask 777 to allow each client to create temporary files.
  • Developer for z/OS writes log messages in the z/OS Explorer log files located in /var/zexpl/zexpl/logs/$LOGNAME. The actual location is specified in the z/OS Explorer configuration. The files within are maintained by z/OS Explorer and Developer for z/OS product code.
  • /var/zexpl/pushtoclient/ holds host-based project information, client configuration files and client product update information that is pushed to the client upon connection to the host. The actual location is specified in pushtoclient.properties (variable pushtoclient.folder). The files within are maintained by a Developer for z/OS client administrator.
    Note: The host components of Developer for z/OS are shared by multiple products, and the data in /var/zexpl/pushtoclient/projects is not used by Developer for z/OS.
  • /var/zexpl/pushtoclient/projects/ holds the host-based project definition files. The actual location is specified in /var/zexpl/pushtoclient/keymapping.xml, which is created and maintained by a Developer for z/OS client administrator. The files within are maintained by a project manager or lead developer.