Installation and Configuration

This document covers the following topics:

Server Prerequisites

The following Software AG products must be installed on the server:

  • According to the desired type of communication between the Natural for Windows client with the remote Natural mainframe server environment, one of the following must be installed:

    • Natural Development Server (NDV)* is required for working in a Natural Single Point of Development (SPoD) environment, or

    • EntireX Communicator (EXX)* is required for working in a Natural Remote Procedure Call (RPC) environment.

  • Natural ISPF (ISP) 8.2 or above.

  • System Automation Tools (SAT)*.

  • Entire System Server (NPR)*.

  • Natural for Mainframes (NAT)**, including the Entire System Server Interface (ESX). See Installing the Entire System Server Interface in the Installation documentation which is provided with Natural for Mainframes.

* The required version of Natural Development Server or EntireX Communicator, and of System Automation Tools and Entire System Server depends on the installed Natural version. See the Release Notes which are provided with Natural for Mainframes.

** The required Natural version depends on the Natural ISPF version running on your system.

If using Natural Roll Server, the minimum roll slot size for Roll Server must be 300KB.

Installation on Windows

Mainframe Navigation can optionally be installed with Natural for Windows. It needs to be installed with either the Natural development environment or the Natural runtime environment. If Mainframe Navigation has not yet been installed, proceed as described below. For more information, see the Natural for Windows installation documentation.

Start of instruction setTo install and configure Mainframe Navigation on your local machine

  1. Start the Software AG Installer and specify all required information on the different panels.

  2. When the product selection tree is shown, expand the Natural Products > Natural node.

  3. Select Runtime Environment and/or Development Environment.

    If you want to work in a Natural Single Point of Development (SPoD) environment, make sure that Development Environment is selected.

    Instead of working with SPoD, you can also work in a Natural Remote Procedure Call (RPC) environment using EntireX Communicator (EXX). Via the RPC communication, you can combine Mainframe Navigation with Output Management GUI Client and Entire Operations GUI Client.

  4. Select Entire Systems Management. This installs Mainframe Navigation, Output Management GUI Client and Entire Operations GUI Client.

  5. Choose the Next button to continue with the installation.

Initializing Mainframe Navigation

Only required if you want to work in an RPC environment using EntireX Communicator. Not required for a SPoD environment.

When the Software AG Installer has finished the installation, you have to initialize Mainframe Navigation. Only initialized clients will be shown in the Entire Systems Management application window.

Start of instruction setTo initialize Mainframe Navigation

  1. Choose All Programs > Software AG > Administration > ESM Configuration for Natural n.n from the Windows Start menu.

    where n.n stands for the current version number. The Start menu group name (by default, this is "Software AG") can be changed during the installation.

  2. In the resulting dialog box, open the drop-down list box next to Mainframe Navigation and select initialize.

  3. Choose the OK button.

Configuring the Connection to the RPC Server Environment

Only required if you want to work in an RPC environment using EntireX Communicator. Not required for a SPoD environment.

In order to configure the connection to your Entire Systems Management (ESM) RPC server environment, you have to change the parameter file SYSESM2 using the Natural Configuration Utility (see the Natural for Windows documentation for detailed information on how to use this utility). This parameter file is available when an ESM product such as Mainframe Navigation has been installed; it is only used for RPC.

In addition, you have to modify the configuration files services and hosts in your local file system.

Start of instruction setTo change the parameter file SYSESM2

  1. Start the Natural Configuration Utility.

  2. In the tree on the left side of the Configuration Utility window, expand the node for the parameter file SYSESM2.

  3. Expand the node Client/Server.

  4. Select the node Remote Procedure Call.

  5. On the right of the window, select the RPC (Client) page.

  6. Enter the name of your ESM RPC default server (DFS) in the Server name text box (this replaces the default value "ESMSRV").

  7. Enter the name of your communication broker node in the Server node text box (this replaces the default value "BKR001").

  8. Save the parameter file and exit the Natural Configuration Utility.

Start of instruction setTo modify the configuration files services and hosts

The configuration files services and hosts are typically located in the subdirectory system32\drivers\etc of your Windows directory. It is recommended that you back up your configuration files before you commence with the following steps.

  1. Switch to your local machine.

  2. Open the services configuration file in a text editor and insert the following line: 

    server-node port-number/tcp

    where server-node is the host name of your communication broker node as defined in the Configuration Utility (see above) and port-number is the port number to be used.

    Note:
    The port number determines where the additional line must be inserted in the services configuration file. For example, if an entry with the port number 2500 exists and is followed by an entry with the port number 4000, you have to insert an additional line between these entries for the port 3800.

    To allow resolution of a symbolic network name of your broker node, this name must be resolved by your LAN name server or in your local hosts configuration file.

  3. Open the hosts configuration file in a text editor and insert the following line: 

    ip-address server-node

    where ip-address is the IP address of your communication broker node in your LAN and server-node is the name of your broker node.

Installation on Mainframe Servers

There is no special installation required. Make sure that the products listed under Prerequisites are installed on the mainframe server.

If you want to access multiple Entire System Servers with the same SYSESM2 parameter file, you can use the dynamic parameter DFS to overwrite the settings in the parameter file, for example, DFS=(ESM62SRV,BKR062,L). For further information on the DFS parameter, see the Parameter Reference in the Natural for Mainframes documentation.

Defining the Entire System Server Nodes

When all required products are installed on the mainframe server, you must define all Entire System Server nodes you wish to access with Mainframe Navigation. This is done with Natural ISPF. For detailed information, refer to the section System Configuration > Entire System Server Node Table in the Natural ISPF Administration Guide.

Ensure that the Entire System Server node table has been edited (at least a minor modification) and saved (command END). Example: 

---------------------------- UPDATE NODES TABLE -------------------------------
COMMAND ===>                                                                   
                                                                               
                                                                               
    Node   Description           Name                                          
    -----  --------------------  ----                                          
    ___69  E-machine(Prod) MVS_  DAEE                                          
    __148  F-machine(Dev.) MVS_  DAEF                                          
    __248  A-machine(Demo) MVS_  DAEA                                          
    50013  Test MVS____________  ESY5999 ENTI NOT ACTIVE  
    __194  OSD5 SI15___________  7.500-S115-2 
    __193  VSE X-machine_______  VSE.ESA.SUPX                                  
    55521  Test VSE____________  VSE.ESA.TEST                                  
    _____  ____________________

Ensure that the access to all nodes is active and works without any warnings (for example, ESY5…) when saving the nodes table.

Configuring Natural ISPF on the Mainframe Server

Make sure that Natural ISPF is configured correctly on your mainframe server:

  • Ensure that the installed subsystems are defined in the configuration member CONFIG: your site's operating systems, Natural and System Automation Tools (SAT).

    For detailed information, refer to the section System Configuration > Editing the Configuration Member CONFIG > Defining Installed Subsystems in the Natural ISPF Administration Guide.

  • Ensure that the authorization table of the user who should use Mainframe Navigation has a defined status (compare the Auth attribute in the Defined Characteristics column). This can be done by defining the authorization table for the user explicitly, or it can be inherited from a prefix definition, from a (Natural Security-based) user group definition or from the default user definition (which is indicated by an asterisk (*)).

    For detailed information, refer to the section User Definitions in the Natural ISPF Administration Guide.