Definitions for Entire System Server - SATSRV

This section only applies to Entire System Server nodes on UNIX and Windows.

After the installation of Entire Operations or Entire Output Management, you have to create a Natural text object SATSRV in the library SYSSATU, as described in this section.

You have to customize the text object SATSRV to contain the required parameter definitions for System Automation Tools.

For each service that is to be accessed via EntireX Broker, you need one section of parameter definitions in SATSRV. The entries in SATSRV have the format:

node-name   SATSRV TYPE=ACI
                 BROKER-ID=broker-id
                 SERVER-CLASS=NPR
                 SERVER-NAME=server-name
                 SERVICE=service-name
                 USER-ID=user-id
                 WAIT-TIME=seconds
                 LOCALE-STRING=locale_string

The individual parameters are described below.

For example definitions, see the text object SATSRVEX in the library SYSSATU, which can be used as a template for SATSRV.

To access a service in local mode (without using EntireX Broker), certain parameter definitions are required. Copy the second section of the example in SATSRVEX into SATSRV and replace service-name with a name of your choice.

Creating SATSRV for the First Time

If you are installing System Automation Tools for the first time, create SATSRV as follows:

Invoke Natural and log on to the library SYSSATU.
Issue the command EDIT SATSRVEX.
Issue the command SAVE SATSRV.

SATSRV Parameters

Parameter	Explanation
`node-name`	It is recommended that the same name as the `server-name` be used. For Entire Operations, see note below.
`TYPE`	The type of communication: It must always be `ACI`.
`BROKER-ID`	Corresponds to the parameter `BROKER-ID` specified in the EntireX Broker attribute file. For information on the maximum length of the `BROKER-ID` parameter, see the EntireX Broker documentation. `broker-id` is the name of the EntireX Broker under which the service is started, for example, `BRK034`. If Entire Operations or Entire Output Management is executed in a UNIX or a Windows environment, for `broker-id` the following syntax can be used: `host:port:TCP`. Example: `BROKER-ID=ibm1:3800:TCP` Note: A `SATBKR` definition will only be used by System Automation Tools if the `BROKER-ID` specified in `SATBKR` is the same as the one specified here.
`SERVER-CLASS`	Corresponds to the parameter `CLASS` specified in the EntireX Broker attribute file.
`SERVER-NAME`	Corresponds to the parameter `SERVER` in the SDPA structure. `server-name` is the name of a mainframe or a UNIX server. This is the host name of the machine on which the Broker Service is to be executed. The `'Server='` specification in the `npr.ini` file must be identical to the `server-name` specified here. For Entire Operations, see note below.
`SERVICE`	Corresponds to the parameter `SERVICE` specified in the EntireX Broker attribute file. `service-name` is the name of the EntireX Broker Service.
`USER-ID`	This parameter is obsolete. For compatibility reasons, however, it can remain part of `SATSRV`; that is, you need not remove it.
`WAIT-TIME`	Corresponds to the parameter `WAIT` specified in the EntireX Broker attribute file. `seconds` is the 3-character wait time in seconds, for example, `60S`.
`LOCALE-STRING`	Corresponds to the parameter `LOCALE_STRING` in the SDPA structure. The parameter is important for character-set translation and conversion.

Note for Entire Operations:

The node-name and the server-name must correspond to the node names specified in the Entire Operations node table; see Definition of Nodes in the Entire Operations Administration documentation.

Also,node-name and service-name must correspond to a section name within the npr.ini file on the target system. We recommend that the same identifiers be used for node names and service names.