Entire Operations in Distributed Environments

This document covers the following topics:

Mixed Environments

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

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

Examples for the Required Service Definitions to Access a UNIX or Windows Node

This section covers the following topics:

Definitions for Node Where Entire Operations Resides

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 Controlled 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 above definitions are required to access mainframe resources and jobs via Entire System Server. There are only three prerequisites for this type of remote access:

  1. The desired Entire System Server node must be accessible via Entire Net-Work.

  2. The desired Entire System Server node on the mainframe must be version 2.1.2 or above. If this node is running in a BS2000 environment, zap XC21044 (problem tape XC12P1) is also required.