Adabas Cluster Services requires Entire Net-Work to provide communication across operating system images between users (including utilities and Adabas Online System) and the nuclei in the Adabas cluster as well as among ADACOM jobs. Communication among the cluster nuclei is performed via XCF.
Note:
ADACOM and several Adabas cluster nuclei could run within a single
operating system image without Entire Net-Work, but there could then be no
application programs for that database in any other image.
This document covers the following topics:
If you are not currently running Entire Net-Work, you must install the Entire Net-Work limited (WDXvrs) library supplied on the Adabas Cluster Services installation tape. This library includes Entire Net-Work's XCF line driver (also known as the Entire Net-Work XCF Option).
The Adabas limited (WALvrs) libraries provide the Adabas components necessary to support the Entire Net-Work connection on a node that participates in an Adabas sysplex cluster (that is, has cluster users) but does not have Adabas installed.
If you are currently running Entire Net-Work, you can use your existing system as long as the following conditions are met:
An Entire Net-Work node is running on each operating system image that will also be running a cluster nucleus and/or ADACOM.
The Entire Net-Work nodes supporting the cluster nuclei are all interconnected using one of the currently supported Entire Net-Work line drivers: XCF, VTAM, CTC, or TCP/IP.
The Entire Net-Work nodes use the same SVCCLU linked with the ADASVC that is used for the Adabas Cluster Services components they support.
If these conditions are not met, you cannot use your existing Entire Net-Work configuration. You must then use the Entire Net-Work limited library supplied on the Adabas Cluster Services installation tape.
You may incorporate the XCF line driver (also known as the Entire Net-Work XCF Option) into your existing Entire Net-Work configuration. The XCF line driver provides performance comparable to the CTC line driver.
When using the XCF line driver, the physical connection mechanism between Entire Net-Work nodes is transparent to Entire Net-Work. The connections may be over CTC links, XCF links, or both.
The connection mechanism/methods are defined by the system programmer using the COUPLExx SYS1.PARMLIB member and the coupling facility resource management (CFRM) policy.
If you are installing the XCF line driver into an existing set of Entire Net-Work nodes, Software AG recommends that you concatenate the Entire Net-Work limited libraries from the Adabas Cluster Services tape in front of the existing Entire Net-Work library in the STEPLIB sequence.
Concatenate the Adabas Cluster Services library ahead of the Adabas load library.
