Entire Operations in Client/Server Environments

#### Search Results

Search

# Entire Operations in Client/Server Environments

This document covers the following topics:

- Accessing UNIX/Windows Machines from the Mainframe

- General Prerequisites

- Required Parameter Definitions

- Example Scenario for File Definitions

## Accessing UNIX/Windows Machines from the Mainframe

To access a UNIX or Windows machine from the mainframe

- Define services and nodes on both mainframe and UNIX or Windows systems. For information on defining UNIX or Windows nodes within Entire Operations, see the section UNIX and Windows Node Definitions in the Administration documentation. This describes where to define corresponding services and EntireX Broker parameters.

## General Prerequisites

Make sure that an EntireX Broker Stub (e.g. NATETBvr) is linked into the Natural batch/ subtask module.

## Required Parameter Definitions

If you want to use Entire System Server nodes on UNIX and Windows, the following definitions are required in the Natural object SATSRV contained in the SYSSATU library:

- Definition | Meaning
  --- | ---
  BROKER-ID= ..... | EntireX Broker ID.
  SERVER-CLASS=NPR | Class of the Entire System Server.
  SERVER-NAME= .... | Name (in upper case) of the Entire System Server.
  SERVICE=service | Service (in lower case) of the Entire System Server.

  For more information on SATSRV, see the section SATSRV Parameters in the section SATSRV: SAT Definitions for Entire System Server Nodes on UNIX and Windows in the Installation on Mainframe Platforms section of the System Automation Tools documentation.

- For EntireX Broker, in the attribute file:

  Definition | Meaning
  --- | ---
  BROKER-ID= ..... | EntireX Broker ID.
  CLASS=NPR | Class of the Entire System Server.
  SERVER= .... | Name (in upper case) of the Entire System Server.
  SERVICE=service | Service (in lower case) of the Entire System Server.

  These definitions must be created on the platform where EntireX Broker is installed (either mainframe or UNIX or Windows).

  For information on customizing the EntireX Broker attribute file and using the Entire System Server/UNIX or Windows npr.ini initialization file, see the appropriate Entire System Server Installation documentation.

## Example Scenario for File Definitions

This section covers the following topics:

- Overview of Required File Definitions

- Mainframe Definitions for this Example

- Middleware Definitions for this Example

- Server Definitions

### Overview of Required File Definitions

### Mainframe Definitions for this Example

> SYSSATU/SATSRV

>   In the Natural SATSRV object in the SYSSATU library, a section must exist starting with:

>       node-name SATSRV TYPE=ACI

>   In this line, node-name must be replaced by the identifier specified in the corresponding field when defining the node within Entire Operations (see the field Node Name in the Administration documentation). The required definitions for the above example would be read as follows:

>       NODE123 SATSRV   TYPE=ACI
>                        BROKER-ID=BKR034
>                        SERVER-NAME=HP001
>                        SERVER-CLASS=NPR
>                        SERVICE=NPR-DEMO1
>       .
>       .

### Middleware Definitions for this Example

These definitions apply either to mainframe or UNIX or Windows.

> EntireX Broker Attribute File

>   The following is an example for Entire Operations with:

>       SERVER=HP001
>       CLASS=NPR
>       SERVICE=NPR-DEMO1
>       .
>       .

### Server Definitions

The following definitions in the file npr.ini apply to a UNIX or Windows system. They are required for the example above:

    NPR-DEMO1

    Local_node=HP001
    Integration_Mechanism=ETB,BKR034
    .
    .