Installation Overview

This section contains general information that applies to all Entire Net-Work installations. It covers the following topics:


Installation Checklist

The following checklist outlines the steps for installing Entire Net-Work:

  1. Prepare the environment as described in the section specific to the operating system and the line driver.

    For information regarding Software AG product compatibility with IBM platforms and any IBM requirements for Software AG products, please review the Product Compatibility for IBM Platforms web page.

  2. Unload the installation libraries from the installation media. Refer to the Software AG Product Delivery Report for specific data set sequence numbers.

  3. Prepare and install the product license file.

  4. Prepare Entire Net-Work JCL and parameter statements.

  5. Install the Adabas router, if necessary.

  6. Complete any access method-related work; for example, updating VTAM definitions or installing a channel-to-channel adapter.

  7. Start Entire Net-Work and establish connectivity with the partner nodes.

Using System Maintenance Aid

If you use Software AG's System Maintenance Aid (SMA), refer to the System Maintenance Aid manual for information about the installation process.

The installation procedures described in this section correspond to the jobs that SMA creates to install the product.

If you do not use SMA, you can modify and use the sample JCL to unload the Entire Net-Work libraries from the installation media. Sample JCL is provided in each of the platform-specific installation procedure sections.

The Entire Net-Work Installation Media

Refer to the Software AG Product Delivery Report that accompanies the installation media for information about the volume serial number, density, media type, data set names, and data set sequence numbers of the media.

The media contains the installation data sets, a data set required by SMA, and one or more data sets containing maintenance fixes. Only the load modules required to run the Entire Net-Work line drivers purchased for your environment are included on the installation media.

Contents of the Release Media

The following table describes most of the libraries included on the release media. Once you have unloaded the libraries from the media, you can change these names as required by your site, but the following lists the names that are delivered when you purchase Entire Net-Work.

Note:
Some of the libraries listed below may not appear on your release media. If this is the case, it is likely that an update to that library was not necessary for the release.

Library Name Description
APSvrs.LDnn One or more Software AG internal libraries. The vrs in the library name represents the version of the internal library code, which is not necessarily the same as the version of Entire Net-Work
BTEvrs.LDnn A Software AG internal library. The vrs in the library name represents the version of the internal library code, which is not necessarily the same as the version of Entire Net-Work
MLCvrs.JOBS The sample job library for Software AG's common mainframe license check software. The vrs in the library name represents the version of the license check software, which is not necessarily the same as the version of Entire Net-Work.
MLCvrs.LOAD The load library for Software AG's common mainframe license check software. The vrs in the library name represents the version of the license check software, which is not necessarily the same as the version of Entire Net-Work.
WAFvrs.JOBS The sample z/OS job library for Entire Net-Work SAF Security. The vrs in the library name represents the version of Entire Net-Work SAF Security.
WAFvrs.LOAD The z/OS load library for Entire Net-Work SAF Security. The vrs in the library name represents the version of Entire Net-Work SAF Security.
WAFvrs.SRCE The z/OS source library for Entire Net-Work SAF Security. The vrs in the library name represents the version of Entire Net-Work SAF Security.
WALvrs.JOBS The sample z/OS job library for Adabas Limited Load Library, containing code for Adabas components shared by Adabas and other Software AG products. The vrs in the library name represents the version of Adabas Limited Load Library.
WALvrs.LOAD The z/OS load library for Adabas Limited Load Library, containing code for Adabas components shared by Adabas and other Software AG products. The vrs in the library name represents the version of Adabas Limited Load Library.
WALvrs.SRCE The z/OS source library for Adabas Limited Load Library, containing code for Adabas components shared by Adabas and other Software AG products. The vrs in the library name represents the version of Adabas Limited Load Library.
WCCvrs.LOAD The z/OS load library for Entire Net-Work CTC Option. The vrs in the library name represents the version of Entire Net-Work CTC Option.
WCPvrs.LOAD The z/OS load library for Entire Net-Work. The vrs in the library name represents the version of Entire Net-Work.
WCPvrs.MVSTAR The z/OS UNIX tar file for Entire Net-Work. The vrs in the file name represents the version of Entire Net-Work. This file is used to create the folder structure with subdirectories and files required for the Adabas Directory Server (ADI).
WCPvrs.SRCE The z/OS source library for Entire Net-Work. The vrs in the library name represents the version of Entire Net-Work.
WDXvrs.LOAD The z/OS load library for Entire Net-Work Limited Load. The vrs in the library name represents the version of Entire Net-Work Limited Load.
WSLvrs.LIBR The z/VSE library for Encryption for Entire Net-Work. The vrs in the library name represents the version of Encryption for Entire Net-Work, which is not necessarily the same as the version of Entire Net-Work.
WSLvrs.LOAD The z/OS load library for Encryption for Entire Net-Work. The vrs in the library name represents the version of Encryption for Entire Net-Work, which is not necessarily the same as the version of Entire Net-Work.
WTCvrs.LIBR The z/VSE load library for Entire Net-Work TCP/IP Option. The vrs in the library name represents the version of Entire Net-Work TCP/IP Option.
WTCvrs.LOAD The z/OS load library for Entire Net-Work TCP/IP Option. The vrs in the library name represents the version of Entire Net-Work TCP/IP Option.
WTCvrs.MOD The BS2000 load library for Entire Net-Work TCP/IP Option. The vrs in the library name represents the version of Entire Net-Work TCP/IP Option.
WXFvrs.LOAD The z/OS load library for Entire Net-Work XCF Option. The vrs in the library name represents the version of Entire Net-Work XCF Option.

Running Entire Net-Work

Starting the Entire Net-Work Job/Task

When execution JCL, including the ADARUN and Entire Net-Work parameter statements, is created for each node, and all access method-specific definitions and installation steps are completed, Entire Net-Work can be started.

The execution job or procedure for Entire Net-Work must be started on each of the participating nodes. Once started, Entire Net-Work determines the interregion communications environment on its node, connects to neighboring nodes through the defined links, and exchanges all relevant information with the other nodes during the "handshaking" process following link connection.

While the Entire Net-Work tasks are active and connected, user programs on any node can access all active targets on any other node, regardless of the targets' locations.

If a link fails or cannot be connected properly, Entire Net-Work searches for possible alternate routes to complete the call. Once a disconnected link becomes available again, it is automatically considered for traffic.

Specifying the Control Statements

There are five types of Entire Net-Work control statements:

  • ADARUN parameters define the interregion communications environment. Some ADARUN parameters are the same as for Adabas; others are similar, but are designed specifically for Entire Net-Work. For more information, see the section ADARUN Parameters

  • NODE statements define the node's name and operating characteristics. For more information, see the section Entire Net-Work NODE Statements.

  • DRIVER statements define the line driver type to be loaded. For more information, see the section Entire Net-Work DRIVER Statements.

  • LINK statements define the links to other nodes. For more information, see the section Entire Net-Work LINK Statements

  • TRANSDEF statements define special conversion requirements. For more information, see the section Translation Definition Statements.