Entire Operations in Distributed Environments

#### Search Results

Search

# Entire Operations in Distributed Environments

Entire Operations can run in mixed mainframe/UNIX/Windows environments.

The Entire Operations Monitor and the Entire Operations system files can be installed on a mainframe or UNIX machine, the managed environments on the other hand may run under any mainframe or UNIX or Windows operating system.

This section provides examples of service definitions required to access a UNIX or Windows node.

This document covers the following topics:

- Definitions for Nodes Where Entire Operations Installed

- Definitions for Managed Environments - UNIX

- Communication with Mainframe Nodes

## Definitions for Nodes Where Entire Operations Installed

> SYSSATU/SATSRV

>   The customization of SYSSATU/SATSRV is described in the relevant section of the System Automation Tools documentation. The following is an example for Entire Operations with:

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

> EntireX Broker

>   The customization of EntireX Broker is described in Customize EntireX Broker in the section Completing the Installation in the Entire System Server documentation. The following is an example for Entire Operations with:

>       SERVER   = HP001F
>       CLASS    = NPR
>       SERVICE  = nprdemo
>       .
>       .

## Definitions for Managed Environments - UNIX

Definition of the Entire System Server/UNIX initialization file npr.ini is described in Customize the NPR Server in the section Completing the Installation in the Entire System Server documentation. The following is an example for Entire Operations (see BS2000 Work File Extensions) with:

    [nprdemo]
    Local_node            = HP001
    Integration_Mechanism = ETB,BKR034
    .
    .

## Communication with Mainframe Nodes

None of the definitions described in the previous section are required to access mainframe resources and jobs via Entire System Server. However, the desired Entire System Server node must be accessible via Entire Net-Work.

### Nodes on z/OS and z/VSE Systems

The desired mainframe nodes must be accessible via Entire Net-Work.

### Nodes on BS2000 Systems

The desired mainframe nodes must be accessible

- either via Entire Net-Work

- or via the Entire Systems Management Adapter (ESA).

Both access methods may be used in parallel for different BS2000 nodes.

### Node Access via the Entire Systems Management Adapter (ESA)

Please follow the installation instructions for the Entire Systems Management Adapter (ESA).

To define a BS2000 node as an ESA node, refer to the section Enable Mapping of Node IDs to Host Names and Port Numbers in Setting Up the Entire System Server Interface in the Entire Systems Management Adapter documentation.

### Additional Settings in the Entire Operations Online and Monitor Scripts

If you want to use ESA BS2000 nodes, you must set the environment variable `NAT_ESX_NODE_MAPPING` in the Entire Operations startup scripts for online sessions, the Entire Operations Monitor tasks, and the RPC server tasks prior to the invocation of Natural. In one Entire Operations installation, it must point to the same file in all scripts.

Code snippet (example for sh or bash):

    NAT_ESX_NODE_MAPPING=/home/sag/esa_nodes.txt
    export NAT_ESX_NODE_MAPPING
    if [ ! -f $NAT_ESX_NODE_MAPPING ]; then
    	echo "$NAT_ESX_NODE_MAPPING not found"
    	exit 1
    fi

The behavior and the programming interface of ESA nodes is principally the same as for Entire System Server (NPR) nodes.

### On this page

- Definitions for Nodes Where Entire Operations Installed
- Definitions for Managed Environments - UNIX
- Communication with Mainframe Nodes