Using FOCUS to Access Data on a Server

In this section:

How to:

This topic describes processing alternatives when using FOCUS to access data on a server:

Remote Execution

This approach allows you to read, analyze, consolidate, and update remote data by sending the FOCUS stack to a server.

You can also execute FOCEXECs stored on the server (called Remote Procedures), using a process known as a Remote Procedure Call (RPC).

In remote execution, the server typically handles data processing, while the client does the request generation and data presentation.

To return report output to a file on the FOCUS Client, you can use the PCHOLD (HOLD AT CLIENT) command in your report request.

Distributed Execution

In Distributed Execution (also referred to as the Server Data Adapter), data retrieved from the server is processed on the client. Here, the server is primarily involved with data access. Distributed Execution shields end users from needing to know where data actually resides through a mechanism known as location transparency.

When you use FOCUS as a client to a Reporting Server, you can control whether the:

Syntax: How to Prevent Source Code From Displaying in Batch Output

SET NOREMOTEECHO = {ON|OFF}

where:

ON

Suppresses FOCEXEC source code from displaying in the batch output.

OFF

Displays the code. This is the default value.

Syntax: How to Control USAGE Attributes in a HOLD Master File

SQL EDA SET USAGEFORMAT {ON|OFF}

where:

ON

USAGE formats and edit options in the HOLD Master File match those in the original Master File.

OFF

Causes USAGE formats of HOLD Master Files to be defined based on the data string that is returned by the Server API.

For example, a field described as P8.2 in the original Master File is described as P10.2 in the HOLD Master File. The additional bytes account for the decimal point as well as a minus sign in the case of a negative value. This is the default value.

Establishing and Configuring the FOCUS User Environment

Startup FOCEXECs can log FOCUS users onto a remote server and establish environmental conditions for a session. PROFILE FOCEXECs can also establish environmental conditions or build menu shells of user options.

On the server, the PROFILE FOCEXEC can establish the working environment for the Reporting Server for z/OS—for example, setting WIDTH and PANEL parameters for reporting.

To use a Reporting Server with FOCUS for Mainframe, you must have the following products installed:

Server Configuration File

You must have a configuration file allocated to ddname EDACS3, EDACFG (or CONFIG) to use either remote execution or distributed execution (distributed execution is also called SUFFIX=EDA). It is possible to switch back and forth between these execution techniques in your session.

DNS Names Support

How to:

The FOCUS Client configuration file can identify a server by host name or IP address.

The Domain Name System (DNS) is a global network of servers that translate host names, such as www.informationbuilders.com, into IP addresses.

Syntax: How to Invoke DNS Names Support

The syntax for specifying a host name in the client configuration file for TCP/IP is

HOST = hostname

where:

hostname

Is the name of the host where the server resides.

Example: Using DNS Names Support

The following client configuration file is used for connecting to the host named IBIMVS:

NAME = EDA CLIENT USING CS/3 TCP/IP
NODE = TCPOUT
  BEGIN
 ;  TRACE = 31
    PROTOCOL = TCP
    CLASS = CLIENT
    HOST = IBIMVS       ; DNS NAME OF HOST
    SERVICE = 2459      ; PORT NUMBER OF SERVER
  END

Information Builders