x

How to: Filter Data Sources by Owner/Schema

An owner/schema selector for choosing a data source filter is available on the Web Console. It allows you to choose from a list of existing DBMS owners/schemas. This feature is available for Microsoft SQL, DB2, Oracle, and Sybase data sources.

Top of page

x

The z/OS PDS server supports the JSCOM3 Listener.

This enables the following features:

• Server-side graphics
• Adobe® Flex®

It also enables the following Java-based adapters:

• Call Java
• EJB
• JDBC
• Microsoft SQL Server

x

When the effective number of CPUs (cores) on a computer exceeds the number allowed by the server license, depending upon the license, either the server will not start or users will be given warnings in edaprint.log and at Web Console or Data Management Console login.

For Windows:

To correct the situation, the installation site has two choices:

• Install the server on a computer with a physical number of CPUs/cores that is less than or equal to the license amount.
• Create a virtual environment using VMware or Microsoft Virtual PC with a number of cores that matches the license requirement, and run the server instance under one of these virtualization options.

Note: Running multiple instances of the server (each under a limited virtual processor set) or adding processors to the virtual set after the server is running, constitutes a license violation.

Microsoft Virtual PC only supports single CPU/core virtualization, while VMware supports multiple CPU/cores. Both offer converter tools to “re-image" a PC into a virtualization. At server installation time, if a site is in violation, the site has the option of continuing (and converting to virtualization afterwards) or stopping the initial install to reattempt the installation in an environment that is already virtualized correctly.

For UNIX:

The Solaris, HP-UX, Linux, and AIX versions of the server can be configured to use fewer CPUs than a machine physically has. This configuration requires operating system commands that vary by platform.

Under this change and certain license codes, a server will only start if the actual physical or effective CPU quantity is greater than or equal to the licensed number of CPUs. License codes that only give CPU warnings, may also be started in the same manner to stop the warning.

The commands and steps vary by operating system:

• psrset for Solaris and HP-UX
• taskset for Linux
• mkrset/execrset for AIX

It is up to the customer to use these commands to configure the environment and start the server (as documented in the server installation guide) when there are fewer licensed CPUs than physical CPUs.

For specific steps by platform, see Limiting CPU Use on Machines With Multiple CPUs in the Server Installation for UNIX chapter of the Server Installation manual.

x

In OpenVMS 8.x, some DBMS vendors changed their products to use IEEE floating point for single (F)/double (D) float data, while others have retained use of G_FLOAT float point or depend upon the application itself. To support these varying float type sources, OpenVMS 8.x servers now use the SET VMSFLOATCNV = IEEE/G-FLOAT command to select the float type of the data. The command is used in the server profile (edaprof.prf). Sites that use both IEEE and G_FLOAT data sources will need separate server configurations with the appropriate SET VMSFLOATCNV = IEEE/G-FLOAT command and a hub-sub configuration to allow the joining of data.

Releases prior to 7.7.02 used separate builds to read the different float types. The change saves disk space and maintenance efforts by using a shared single install and the SET command.

For more information, see the Server Installation for OpenVMS chapter in the Server Installation manual.