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

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 a Mainframe Node

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.