Installation for ZFS and PDS

Before installing, read the topics in this section for:

  • Guidance on choosing how to deploy on ZFS in UNIX System Services or PDS.
  • Configuration information common to both deployments, such as the location of different types of server files.
  • An overview of which steps you will need to perform to install your server.

Choosing How to Deploy

z/OS provides you with the following deployment environment: a choice of deployment environments. You can deploy using either:

  • The z/OS File System (ZFS) on UNIX System Services (USS). The ZFS-deployed software stores executable code and user data on the ZFS. Security is provided by UNIX file security and by your z/OS security package, such as RACF, eTrust CA-Top Secret®, or eTrust CA-ACF2®. You install from ISPF and start it using JCL. All other processes occur under USS.
  • Partitioned data sets (PDS) which deploys software in partitioned data sets. The PDS-deployed software provides most features of the ZFS-deployed software, but removes the requirement for interaction with UNIX System Services at installation time and run time. Administration of the software, from a systems perspective, has been streamlined to match that of the classic MVS version of the server (also known as the SSCTL server).

    The PDS deployment environment is designed to support legacy applications and features. New server features that require some ZFS footprint, such as .xlsx support, file uploads, and the stress tool on the WebFOCUS Reporting Server browser interface, will not be available.

    To take advantage of these features, you can either deploy the ZFS version or, alternatively, have a mixed environment, where you create a PDS instance for your legacy applications, and have a small ZFS instance just for the administrator to access the WebFOCUS Reporting Server browser interface features missing in PDS. Both server instances can have a shared mapped application to exchange data seamlessly.

The following table compares the benefits of each way of deploying on z/OS.

Feature

ZFS / USS

PDS

File Management:

Server run-time and configuration files

In the UNIX ZFS file system.

In partitioned data sets (PDSs).

File Management:

User data, metadata, and procedures

In the UNIX ZFS and, optionally, in a PDS.

In a PDS and, optionally, in the UNIX ZFS.

Security

Standard security packages are supported (RACF, eTrust, CA-ACF2®, and eTrust CA-Top Secret).

All directories and files must have their user/group/world attributes correctly set.

A user ID with a UID of 0 (that is, a superuser) is required when running the server with security set to OPSYS or a special UNIXPRIV user ID can be used.

Standard security packages are supported (RACF, eTrust CA-ACF2, and eTrust CA-Top Secret). No additional security is required.

User IDs

A UID of 0 (that is, a superuser) can install, but not administer or connect to, the server.

Each user ID that will install, administer, or connect to the server requires a ZFS segment with sufficient space and appropriate file permissions for the tasks that the ID will perform.

Any user ID can install, administer, and connect to the server.

Adapters

Use a mixture of USS-based and MVS-based libraries/APIs.

Use MVS-based libraries/APIs.

The exception is DBMSs that support only USS-based libraries/APIs, such as Db2 CLI and Java-based adapters, such as Microsoft SQL Server, which use vendor libraries/APIs residing in the hierarchical file system.

Traces and Server Log

Accessible from the WebFOCUS Reporting Server browser interface.

These are available on the JES output of the server job.

WebFOCUS Reporting Server browser interface Stress Tool

Available from the WebFOCUS Reporting Server browser interface.

Feature not available.

Format XLSX and PPTX

Supported

Not Supported

Note: As a workaround, you can SET EXCELSERVURL to point to a ibi™ WebFOCUS® apps context root.

Adobe Flex

Supported

Not Supported

RACF TEMPDSN class

Supported

Supported, except for the FOCCACHE app.

DFM reports stored in approot app

Supported

Not Supported

Use standard DFM data sets instead.

Native ! (bang) USS Operating System commands in applications

Supported

Not Supported

Adapter Flat File via FTP Server

Supported

Not Supported

WebFOCUS Reporting Server browser interface Upload file tool

Supported

Not Supported

PDS deployment also requires each user of the server to be identified to USS by means of a default segment definition. For more information, see Security Providers.

File Locations

The software includes several groups of files used for installation, configuration, and administration. These groups are implemented differently in USS and PDS deployments:

Supplied Files Location (EDAHOME)

The programs and related files are stored in a location referred to as EDAHOME. The installation process copies the software into EDAHOME.

  • In USS deployment, EDAHOME defaults to the following directory and several subdirectories:
    ibi/srv/home
  • In PDS deployment, EDAHOME defaults to the following partitioned data sets:
    high_level_qualifier.P.HOME.WFS

    where:

    high_level_qualifier

    Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV). However, you can use any site-specific value.

    component_type

    Designates the type of server component. The values are:

    Type of ComponentDescription
    ETC

    Script and text files.

    BIN

    Binary-based object files.

    ACX

    Server Access Files.

    MAS

    Server Master Files.

    FEX

    Server procedure (FOCEXEC) files.

    ERR

    Error files.

    LOAD

    Load library.

Configuration Files Location (EDACONF)

The configuration files are stored in a location referred to as EDACONF. Each configured instance has its own EDACONF, which controls the behavior of that instance.

  • In USS deployment, EDACONF defaults to the following directory and several subdirectories:
    ibi/srv/wfs
  • In PDS deployment, EDACONF defaults to the following partitioned data sets:
    high_level_qualifier.WFS.CONF.config_type

    where:

    high_level_qualifier

    Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV). However, you can use any site-specific value.

    config_type

    Designates the type of configuration file.

    The primary configuration file is CFG.

    The WebFOCUS Reporting Server deferred execution configuration files are DEL, RPE, RPF, RPO, RQD, RQF, RQO, and RQP.

Profile Files Location

Server profiles are stored in the following location:

  • In USS deployment, the location is specified in the environment variable EDAPRFU, and defaults to the following directory:
    ibi\profiles
  • In PDS deployment, the location is the following partitioned data set
    high_level_qualifier.WFS.CONF.PRF

    where:

    high_level_qualifier

    Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV92). However, you can use any site-specific value.

    This PDS is allocated in ddname EDAPROF in the server JCL.

Administration Files Location

The file that specifies server administrators is located in:

  • In USS deployment, the location is specified in the environment variable EDAPRFU, and defaults to the following directory:
    ibi\profiles
  • In PDS deployment, the location is member ADMIN of the following partitioned data set
    high_level_qualifier.WFS.CONF.CFG

    where:

    high_level_qualifier

    Is the high-level qualifier for HOME.DATA and for all other data sets that the installation procedure allocates. We recommend that the high-level qualifier reflect the release of the software (for example, IADMIN.SRV92). However, you can use any site-specific value.

    This PDS is allocated to ddname EDACFG in the server JCL.

Application Files Location (APPROOT)

The server application files are stored in a location referred to as APPROOT. APPROOT may be shared by multiple applications.

  • In USS deployment, APROOT defaults to the following directory:
    ibi/apps
  • In PDS deployment, APPROOT defaults to the following partitioned data sets:
    approot.appname.type.DATA

    where:

    approot

    Designates the root qualifier for the server applications.

    appname

    Designates the name of the application. There will be one appname qualifier for each application.

    type

    Designates the type of application component. The values are:

    TypeDescription
    ACCESS

    Access Files.

    ETG

    ibi™ Data Migrator flow information.

    FOCEXEC

    Procedure files.

    FTM

    Temporary files.

    GIF

    Image files (both GIF and JPG).

    HTML

    HTML files.

    MAINTAIN

    Maintain files.

    MASTER

    Master Files.

    WINFORMS

    Forms.

    DTD

    XML DTD files.

    FOCCOMP

    FOCCOMP files.

    FOCSTYLE

    Stylesheet files.

    SQL

    SQL files.

    XML

    XML files.

    XSD

    XML XSD files.

    FOCUS

    ibi™ FOCUS® data files.

Two applications are generated automatically during installation: IBISAMP and BASEAPP, a default application space.

Step-By-Step Installation Overview

The installation process differs somewhat, depending on how you are deploying the software for z/OS. To deploy using:

  • ZFS/USS:   
    1. Installation Requirements for HFS
    2. Installing New on HFS
    3. Starting and Stopping a Server for HFS
    4. DB2 Security Exit Configuration for HFS
    5. MSODDX for DD Translation for User Subroutines

    6. Overriding the Time Zone Setting

    7. Adding a Configuration Instance for HFS
    8. Upgrading Your Server Release for HFS
    9. Performance Considerations for HFS
    10. General Information for a z/OS HFS Installation
    11. Troubleshooting for HFS
  • PDS:
    1. Installation Requirements for PDS
    2. Installing a New Server for PDS
    3. Starting and Stopping a Server for PDS
    4. DB2 Security Exit Configuration for PDS
    5. MSODDX: DDNAME Translation for User Subroutines

    6. Overriding the Time Zone Setting

    7. Adding a Configuration Instance for PDS
    8. Upgrading Your Server Release for PDS
    9. Performance Considerations for PDS
    10. General Information for a z/OS PDS Installation
    11. Troubleshooting for PDS