DataMigrator/Reporting Server > Installation for z/OS > Installation for HFS and PDS

Installation for HFS and PDS

Topics:

Before installing, read the topics in this section for:

Choosing How to Deploy

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

  • The Hierarchical File System (HFS) on UNIX System Services (USS). The HFS-deployed software stores executable code and user data on the HFS. 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 the same rich level of features as the HFS-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 following table compares the benefits of each way of deploying on z/OS.

Feature

HFS / USS

PDS

File Management:

Server run-time and configuration files

In the UNIX Hierarchical file system (HFS).

In partitioned data sets (PDSs).

File Management:

User data, metadata, and procedures

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

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

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 an HFS 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 MS SQL Server, which use vendor libraries/APIs residing in the hierarchical file system.

Traces and Server Log

Accessible from Web Console

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

Web Console Stress Tool

Available from Web Console

Feature not available.

Format XLSX and PPTX

Supported

Not Supported

Note: As a workaround, you can SET EXCELSERVEURL to point to another reporting server that supports these formats.

Adobe Flex

Supported

Not Supported

RACF TEMPDSN class

Supported

Supported except for 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

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 USS Segment Requirements.

File Locations

Topics:

The software includes several groups of files used for installation, configuration, and administration. These groups are implemented differently in HFS 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 HFS deployment, EDAHOME defaults to the following directory and several subdirectories:
    ibi/srv77/home
  • In PDS deployment, EDAHOME defaults to the following partitioned data sets:
    high_level_qualifier.P.HOME.component_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.SRV77). However, you can use any site-specific value.

    component_type

    Designates the type of server component. The values are:

    ETC

    for script and text files.

    		 
    BIN

    for binary-based object files.

    		 
    ACX

    for the server Access Files.

    		 
    MAS

    for the server Master Files.

    		 
    FEX

    for the server procedure (FOCEXEC) files.

    		 
    ERR

    for error files.

    		 
    LOAD

    for the 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 HFS deployment, EDACONF defaults to the following directory and several subdirectories:
    ibi/srv77/product_type
  • In PDS deployment, EDACONF defaults to the following partitioned data sets:
    high_level_qualifier.product_type.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.SRV77). However, you can use any site-specific value.

    product_type

    Designates the software installation type. There will be one product_type for each type of product that you install. The value is determined by your license key: 

    FFS

    for a Full-Function Server

    		 
    DM

    for a DataMigrator Server

    		 
    WFS

    for a WebFOCUS Reporting Server

    		 
    WFM

    for a Shared Application Server for WebFOCUS Maintain

    config_type

    Designates the type of configuration file. The value(s) for:

    The primary configuration file is CFG.

    The Report Server deferred execution configuration files are DEL, REQ, RPE, RPF, RPI, RQD, RQF, RQP, and RSP.

Profile Files Location

Server profiles are stored in the following location:

  • In HFS 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.product_type.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.SRV77). However, you can use any site-specific value.

    product_type

    Designates the software installation type. There will be one product_type qualifier for each type of product that you install. The value is determined by your license key: 

    FFS

    for a Full-Function Server

    		 
    DM

    for a DataMigrator Server

    		 
    WFS

    for a WebFOCUS Reporting Server

    		 
    WFM

    for a Shared Application Server for WebFOCUS Maintain

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

Administration Files Location

The file that specifies server administrators is located in:

  • In HFS 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.product_type.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.SRV77). However, you can use any site-specific value.

    product_type

    Designates the software installation type. There will be one product_type qualifier for each type of product that you install. The value is determined by your license key: 

    FFS

    for a Full-Function Server

    		 
    DM

    for a DataMigrator Server

    		 
    WFS

    for a WebFOCUS Reporting Server

    		 
    WFM

    for a Shared Application Server for WebFOCUS Maintain

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

Application Files Location (APPROOT)

The server application files are stored in a location referred to as APPROOT. APPROOT may be shared by applications created with other Information Builders products.

  • In HFS 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: 

    ACCESS

    for Access Files.

    		 
    ETG

    for DataMigrator flow information.

    		 
    FOCEXEC

    for procedure files.

    		 
    FTM

    for temporary files.

    		 
    GIF

    for image files (both GIF and JPG).

    		 
    HTML

    for HTML files.

    		 
    MAINTAIN

    for Maintain files.

    		 
    MASTER

    for Master Files.

    		 
    WINFORMS

    for forms.

    		 
    DTD

    for XML DTD files.

    		 
    FOCCOMP

    for foccomp files.

    		 
    FOCSTYLE

    for stylesheet files.

    		 
    SQL

    for SQL files.

    		 
    XML

    for XML files.

    		 
    XSD

    for XML XSD files.

    		 
    FOCUS

    for 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:

WebFOCUS

Feedback