Frequently Asked Questions for PDS

Q: Why might someone want to use the PDS deployment?

A: PDS deployment provides the same rich level of features as the USS-deployed server, including the WebFOCUS Reporting Server browser interface, but removes the requirement for interaction with UNIX System Services at installation and run time. It deploys the server software in partitioned data sets. Configuration and user-created source files, such as procedures and metadata, are also stored in PDS libraries.

Administration of the server, from a systems perspective, has been streamlined to match that of the classic MVS version of the server (also known as the SSCTL server). There are fewer user ID requirements for installing and operating the PDS-deployed server than the USS-deployed version, and security management has been simplified.

Q: Does this replace the older MVS server (also known as SSCTL)?

A: The z/OS server with PDS deployment is a migration path from the older MVS server.

Q: Can one refresh a server's installation software that had been deployed one way with software using other type of deployment?

A: No. Each deployment type is independent of the other with regards to installation.

Q: Can both deployments of the server coexist on one z/OS system?

A: Yes.

Q: Can one configure two server instances of the same server, one instance a USS deployment, and the other a PDS deployment?

A: No. Although the media and installation are unified, once the base server software is installed, the two deployment types run separately.

As with the USS deployment, the PDS deployment can have many instances running from the same EDAHOME set of libraries.

Q: Can I monitor server startup by checking the MVS SYSLOG?

A: Yes.

The following messages are written to the SYSLOG when

  • The Server starts successfully:
    (EDA13023) ALL INITIAL SERVERS STARTED
  • The Server does not start:
    (EDA13171) UNABLE TO START IWAY SERVER

Q: What, if anything, does the PDS deployment not support? In what installation implementation?

 

A: The PDS deployment of the server currently does not support the following functions:

  • The WebFOCUS Reporting Server browser interface Run Stress option.
  • Displaying server logs and traces in the WebFOCUS Reporting Server browser interface.
  • Formats XLSX and PPTX.

    Note: As a workaround, you can issue the SET EXCELSERVURL command to point to ibi™ WebFOCUS® Client ibi_apps context root.

    To set this parameter, you can issue the following in a procedure:

    SET EXCELSERVURL = http[s]://servername:port/ibi_apps

    Alternatively, you can issue the following in the WebFOCUS Administration Console:

    IBIF_excelservurl = http[s]://servername:port/ibi_apps

    where:

    servername

    Is the name of the machine where the Application Server is running.

    port

    Is the port used by WebFOCUS to communicate with the Application Server. The default port is 8080. It should also be noted that the protocol may be http or https based on the customer configuration.

  • Adobe Flex.
  • RACF TEMPDSN class—Supported except for FOCCACHE application datasets.