We recommend reading this section from beginning to end before starting the installation process.
The Entire System Server Interface is required if the product Entire Systems Management Adapter 4.1.1 on BS2000 is to be used. The Entire System Server Interface is part of Natural and no extra installation is needed.
Additionally, Natural provides the libraries SYSNPE and
SYSNPR
SYSNPE is the Entire System Server online tutorial which
is provided as a starting help for Entire Systems Management Adapter users. For more information on Entire Systems Management
Adapter,
see Entire Systems Management Adapter documentation.
This document covers the following topics
The Entire System Server Interface provides access to Entire Systems Management Adapter on BS2000 via TCP/IP and on z/OS and z/VSE via Entire Net-Work. For full support of the Entire System Server Interface on z/OS and z/VSE, Entire Net-Work Version 5.8.1 or above is required on the mainframe platforms.
The Entire System Server Interface is not active if you use the standard Natural
configuration settings. The value of the Entire System Server Interface database (Natural profile
parameter ESXDB) is set to 0 by default. To
use theEntire System Server Interface you have to set the value of parameter
ESXDB to 148 using the
Configuration Utility.
In the Configuration Utility, the parameter
ESXDB is assigned in the parameter group
Product Configuration of a parameter file.
Tip:
Locate this parameter by searching for
ESXDB. See Finding a Parameter in the
Configuration Utility documentation for further
information. ESXDB specifies the database ID used for
the DDMs of Entire System Server. This DBID does not specify the target DBID of
Entire System Server requests but tells Natural which DBID is used for the
cataloged Entire System Server DDMs. The effective Entire System Server target
DBID will be specified with the NODE field which is part of all Entire System
Server DDMs.
Important:
Change the value of ESXDB to
148 to run Natural with Entire System Server Interface support. All Entire System Server
DDMs are cataloged with DBID 148. After starting Natural again,
you may access Entire System Server nodes running on the mainframes via Entire
Net-Work. The customization of Entire System Server Interface supports the modification of the Entire
System Server DDMs only.
The access to Entire Systems Management Adapter on BS2000 requires Natural profile parameter CP set to 'ISO-8859-15'.
Mapping of NODE ID’s is needed to access the BS2000 Entire Systems Management Adapter via TCP/IP. The mappings are defined in the so-called node file. See sample file below:
#* comment 120 = tcp://si20:3937 121 = tcp://si21:3937 122 = tcp://si22:3937 148 = tcp://si20:3931 63555 = tcp://si20:3935
Whenever a program is using the Entire System Server DDM’s, the mapping is checked to route the request to the desired host and port. For example. NODE=120 will establish a TCP/IP communication to host si20 and port 3937.
Before starting Natural, you must set the environment variable NAT_ESX_NODE_MAPPING to establish the node mapping file. The full file name must be defined as value of the environment variable. See sample statement for tcsh:
setenv NAT_ESX_NODE_MAPPING /home/sag/nodes.txt