Introduction to Entire Net-Work

#### Search Results

Search

# Introduction to Entire Net-Work

Entire Net-Work for z/OS provides transparent connectivity between client and server programs running on different physical or virtual machines, with potentially different operating systems and hardware architectures. The currently supported set of server programs includes Adabas, Entire System Server, EntireX Communicator, and any other software program that participates in cross-address communications defined by Software AG. A range of client programs are supported, including those written in Natural, the commonly used 4GL provided by Software AG, web-based applications such as Software AG's Jadabas and Tamino, and currently existing Adabas applications.

At its lowest level, Entire Net-Work accepts messages destined for targets or servers on remote systems and delivers them to the appropriate destination. Replies to these requests are then returned to the originating client application, without any change to the application. Entire Net-Work establishes these connections either through its line drivers.

The method of operation and the location and operating characteristics of the servers are fully transparent to the user and the client applications. The servers and applications can be located on any node within the system where Entire Net-Work is installed and communicating. The user's view of the network targets and servers is the same as if they were located on the user's local node. Note that due to possible teleprocessing delays, timing of some transactions may vary.

This section covers the following topics:

- How Entire Net-Work Administration Operates

- Entire Net-Work Components

- Summary of Entire Net-Work Features

## How Entire Net-Work Administration Operates

Entire Net-Work provides transparent support for remote and distributed server processing by supporting the existing Adabas database interface. An Entire Net-Work Client call to Adabas invokes the environment-specific Adabas Link Routine (ADALNKX). This routine issues an interregion call to Adabas through the Adabas router (the Adabas SVC). The router, in turn, locates the Adabas nucleus operating in a separate address space or partition, and adds the user call to the Command Queue (CQ). The Adabas nucleus then selects commands from the Command Queue and performs its normal processing.

Entire Net-Work Client establishes its connections using the Simple Connection Line Driver provided with Entire Net-Work Administration.

## Entire Net-Work Components

Entire Net-Work is installed on each participating host or workstation system requiring client/server capability. The configuration for a given system includes the following components:

- an Entire Net-Work control module;

- control module service routines;

- Simple Connection Line Driver (TCPX); and

Actual network data traffic is controlled by the Simple Connection Line Driver. Each line driver supports multiple connections to other Entire Net-Work Clients.

## Summary of Entire Net-Work Features

The following is an overview of Entire Net-Work Administration features:

- Adabas compatibility
  Entire Net-Work uses Adabas-dependent service routines for the operating system interface as well as for interregion communication, thus avoiding incompatibility.

- Adabas-like "look and feel"
  The similarity between Entire Net-Work and Adabas means that the job control statements for running Entire Net-Work are much like those needed to run Adabas. For example, the EXEC statement invokes the ADARUN program for Entire Net-Work just as it does for Adabas, and the ADARUN parameters for Entire Net-Work are a subset of Adabas parameters.

- Access through e-business connections via the Simple Connection Line Driver
  The Entire Net-Work Simple Connection Line Driver provides communication between Adabas databases (running on z/OS systems) and client applications that use Software AG's new e-business connections. The new e-business connections make use of:

  - an enhanced communication protocol provided by Software AG that links e-business applications with enterprise servers

  - the Adabas Directory Server (ADI).

  Software AG products that support the e-business communication protocol and the Adabas Directory Server currently include Tamino, Jadabas, Entire Net-Work 7 and any other product that transports client requests using Software AG’s ADALNKX module. The underlying transport mechanism is TCP/IP.

  Note
  The Simple Connection Line Driver cannot connect to another Simple Connection Line Driver.

  The Adabas Directory Server is a centralized component that provides all directory information required to communicate between clients and servers and eliminates the need for directory configuration files on every machine. The code for the Adabas Directory Server is included in the Entire Net-Work Client code available on Servline 24. To use the Simple Connection Line Driver, you must have the Adabas Directory Server installed somewhere on your system. If you have already installed this code with another Software AG product, we recommend that you use the installed code, so that your organization uses only one shared Directory Server. For more information about the Adabas Directory Server, read Software AG Directory Server Documentation. The documentation for Entire Net-Work Client is included with its code on Servline 24.

- Unique target ID enforcement
  Entire Net-Work enforces the Adabas requirement that each enterprise-wide target be assigned a unique target ID. (With Adabas, local targets that are introduced may have non-unique IDs.)

- Remote processing of client/server request
  A request can be made from within a Software AG or third party application client program to a server (typically Adabas) located on a remote system, as if the server were running locally with no client changes.

- Single request queue for all remote targets
  Each Entire Net-Work node maintains only one request queue and one attached buffer pool for economical use of buffer storage.

- All buffer sizes allowed
  Buffer size support in Entire Net-Work is comparable to that in Adabas, ensuring that all buffer sizes that are valid for Adabas can also be transmitted to remote nodes.

- Entire Net-Work communication in heterogeneous systems
  Simple Connection Line Drivers support communication between systems with different hardware architectures. This allows for client/server communications to and from Entire Net-Work on Windows.

- Model Links
  The "model" link facility allows users to code one or more model links with parameter values that serve as default values for many partners, instead of coding one LINK statement for each partner. As each partner connects, new control blocks are allocated and initialized from the model link.

- Additional operator commands
  Entire Net-Work's TCPX line driver has the ability to process operator commands that are directed to a specific link or directly to the driver. Some driver and link parameters can be modified with the ALTER operator command while the driver or link is open, thus allowing dynamic reconfiguration of the network. Refer to the specific parameter description for information on possible restrictions about modifying the parameter using the ALTER command.

### On this page

- How Entire Net-Work Administration Operates
- Entire Net-Work Components
- Summary of Entire Net-Work Features