The Entire System Server Interface is required if the Entire System Server or Natural ISPF is to be used.
This document describes the steps for installing the Entire System Server Interface on BS2000. You can choose between default installation (recommended) and customized installation.
For information on installing and using the Entire System Server or Natural ISPF, refer to the relevant product documentation.
When used in this document, the notation
vrs
or
vr
represents the relevant product
version (see also Version in the
Glossary).
A supported version of either of the following products must be installed before you can install the Entire System Server Interface:
Entire System Server or Natural ISPF, version as specified under Software AG Product Versions Required with Natural in the current Natural Release Notes for Mainframes.
See also General Prerequisites and System Support in the section Overview of the Installation Process.
If you want to use the default value settings in the modules
ESYNODTB
and NATPNIP
(used by the Entire System
Server and Natural ISPF), proceed with
Link the Entire System
Server Interface to the Nucleus.
If you do not want to use the default value
settings, edit the modules NATPNIP
and
ESYNODTB
described in this section.
The NATPNIP
module contains the following parameters and
default values:
NAMVIEWP BUFLEN=12288,NUMREQ=5,MAXCBL=3000,MAXEDL=6000,EXTUSER=INIT-USER
The parameters are explained below:
BUFLEN |
Length of all Adabas buffers in bytes |
NUMREQ |
Number of possible nested FIND loops in Natural
calling the Entire System Server
|
MAXCBL |
Complex FIND buffer length
|
MAXEDL |
Editor session buffer length
The default value is 6000, which should be sufficient for an NSPF
editor session and typical incore database applications. However, for large
layouts within an incore database file that value might not be large enough and
the following message is issued:
In this case, the value of |
EXTUSER |
External user ID passed to the Entire System Server for
security checks
See also |
- EXTUSER
The parameter
EXTUSER
describes how to inherit security definitions from an external security system such as RACF, ACF2 and TOP-SECRET.The appropriate parameter setting depends on whether a multi-user address space or a single-user address space is used in your environment:
A multi-user address space provides the option to maintain different user security definitions, for example, one for a CICS and one for a Com-plete user).
A single-user address space supports a subsystem, for example, a Natural subtask for Entire Output Management or Entire Operations Managment, or a Natural RPC, Natural Web/IO Interface or batch server.
Recommended values for
EXTUSER
are:
EXTUSER=INIT-USER
Recommended for a multi-user address space. The contents of the Natural system variable
*INIT-USER
must be identical to the user definiton in the external security system (for example, RACF).The Entire System Server transfers the value of
*INIT-USER
to the external security system, and all calls to security restricted resources are handled under this user ID.In this case, the security definition from a CICS or Com-plete user (for example) is inherited by Entire System Server, and a new logon is not required. If the value of
*INIT-USER
is not found in RACF (for example), an error occurs indicating that a logon is required.(
*INIT-USER
is described in the System Variables documentation.)EXTUSER=USER
Recommended for openUTM. Recommended for a multi-user address space in a Natural Security environment. Processing is similar to
EXTUSER=INIT-USER
except that the Natural system variable*USER
(described in the System Variables documentation) is used.(
*USER
is described in the System Variables documentation.)EXTUSER=ADDRESS-SPACE
Recommended for a TIAM, batch or server environment.
The security description of this address space is inherited for security evaluation.
The ESYNODTB
module contains the following parameters and
default values:
NAMXNOD ID=148,NAME=PRODUCTION-1 NAMXNOD ID=149,NAME=PRODUCTION-2 NAMXNOD ID=1490,NAME=DBID-ABOVE-255,LAST=Y END
The parameters and default values are explained below:
ID |
Entire System Server node number (also known as DBID) |
NAME |
Entire System Server node name |
LAST |
Indicator for last entry in table |
Calls to the Entire System Server from Natural are usually handled with
the NODE
parameter which specifies the node number to be used for
the call, for example:
FIND ACTIVE-JOBS WITH JOB-NAME = 'ADA*' AND NODE = 148
If the node number is defined in the ESYNODTB
module,
alternatively, you can specify the logical name of the required Entire System
Server with the NODE-NAME
parameter, for example:
FIND ACTIVE-JOBS WITH JOB-NAME = 'ADA*' AND NODE-NAME = 'PRODUCTION-2'
If Natural ISPF is used as the INCORE database:
(Job I055, Steps 1106, 1108)
Link the parameter module NATPNIU
(Step 1106 for
openUTM) or NATPNIT
(Step 1108 for TIAM and batch mode).
In this case, the module ESYNODTB
is not required.
If the Entire System Server is used:
(Job I055, Step 1108)
Assemble and link the module ANATPNIU
.
ANATPNIU
must be assembled with NAMVIEWP
EXTUSER=USER
in order to use the Natural Security user ID as user ID for
Entire System Server calls (if no NATPROC-LOGON
is issued).
(Job I055, Step 1106)
Assemble and link the module ANATPNIT
.
NATPNIT
must be assembled with NAMVIEWP
EXTUSER=ADDRESS-SPACE
. The LOGON
user ID will
be used as Entire System Server user ID if no NATPROC-LOGON
has
been issued.
(Job I060, Step 3720)
Link the following Entire System Server Interface modules to the
environment-dependent
nucleus by using the corresponding INCLUDE
statements:
INCLUDE NATPNIP, NATvrs.MOD |
Entire System Server Interface parameters |
INCLUDE ESXNUC, NATvrs.MOD |
Entire System Server Interface module |
INCLUDE NATPRBSU, NATvrs.MOD |
BS2000 service module |
INCLUDE ESYNODTB, NATvrs.MOD |
Optional, node table |
(Optional installation for only batch mode or TIAM.)
This section describes the advantages of Entire System Server in single-user mode and the steps required for installation.
Running the Entire System Server in single-user mode is advantageous, for example, in the following cases:
Executing long running batch jobs comprising a large number of calls to the Entire System Server.
Performing test scenarios using a Natural session under TIAM performing many calls to the Entire System Server, without disturbing the production environment.
Exploring new Entire System Server functionality or versions.
From a Natural point of view, the Entire System Server single-user mode is accessible as Entire System Server node 148, irrespective of whether such a node does already exist on your machine or network.
The following is an example of a Natural program that is running in a single-user environment:
FIND ACTIVE-JOBS WITH NODE = 148 AND JOB-NAME = 'XCOM*'
This statement calls a single-user Entire System Server that runs within the same address-space. Calling a different Entire System Server node that runs elsewhere in the network is possible by using a different node number, as shown in the following example:
FIND ACTIVE-JOBS WITH NODE = 53 AND JOB-NAME = 'NUC*'
This statement calls a multi-user Entire System Server with node number 53 out of the same Natural program which called the single-user Entire System Server session.
Link the optional NATPSNGL
module to the
environment-dependent
nucleus:
INCLUDE NATPSNGL, NATvrs.MOD
This module enables use of single-user mode.
Add the mandatory DDLIB2
card to assign the Entire
System Server load library and the optional PARMS
card to set the
parameters for the Entire System Server:
/ ADD-FILE-LINK LINK-NAME=DDLIB2,FILE-NAME=$SAG.NPRvrs.MOD / ADD-FILE-LINK LINK-NAME=PARMS,FILE-NAME=parameter-file
where parameter-file
is the
name of the Entire System Server parameter file.
The Entire System Server parameter file is read during the execution
of the first Entire System Server user request. You do not have to issue a
LOGON
or LOGOFF
to the
Entire System Server in single-user mode.
Modify your Entire System Server parameter file as required. The
NODE
parameter is ignored since all calls to the Natural node
number 148 are routed through the Entire System Server node used for
single-user mode.