Entire Operations in Client/Server Environments

This document covers the following topics:


Accessing UNIX/Windows Machine from Mainframe

With Version 2.1.1, Entire Operations can be run in mixed mainframe/UNIX or, from Version 3.1.1 onwards, in Windows environments.

Start of instruction set 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. NATETB23) is linked into the Natural batch/ subtask module.

Required Parameter Definitions

In order for you to work with Entire System Server nodes on UNIX and Windows, the following definitions must be present:

  • On the platform where the Entire Operations online system and monitor are running - in the Natural object SATSRV in the SYSSATU library:

    Definition Comment
    BROKER-ID= .....  
    SERVER-CLASS=NPR (must be Entire System Server )
    SERVER-NAME= .... (in upper case)
    SERVICE=service (in lower case)

    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 Comment
    BROKER-ID= .....  
    CLASS=NPR (must be Entire System Server )
    SERVER= .... (in upper case)
    SERVICE=service (in lower case)

    These definitions must be created on the platform where the EntireX Broker is installed (either mainframe or UNIX or Windows). For more information on the customization of the EntireX Broker attribute file, see Step 4.

  • For the file npr.ini, located on the UNIX or Windows system being addressed:

    • the same values as for Natural, above, are used;

    • the service name <service> is written within angle brackets. The attributes follow this.

    Definition of the Entire System Server/UNIX or Windows initialization file npr.ini is described in Step 4: Customize the NPR Server in the Completing the Installation section of the Entire System Server (NPR) documentation.

  • On the UNIX or Windows system being addressed, the Entire System Server must be active.

    • UNIX:
      To activate it, start nprmgr, then enter the command start service <service>. For details, see the section Starting the Server of a UNIX Service.

    • Windows:
      To activate it, choose Control Panel. Then choose Services. Then choose Entire System Server (standard) or Entire System Server (with R/3).

Example Scenario

Overview of Required File Definitions

graphics/ins_file_def.png

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-demo]
Local_node=HP001
Integration_Mechanism=ETB,BKR034
.
.