
	Version 8.1.2	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

Before You Install

This section describes actions which must be taken prior to performing Adabas System Coordinator installation.

Configuration File
Adabas System Coordinator Daemon
Using System Coordinator With Version 8 Link Modules
Use of Unmodified ADALNK

Configuration File

Adabas System Coordinator operates correctly only if the configuration file is continuously available while the client is active. Operational procedures are necessary to ensure that the database where the configuration file (or the optional alternate configuration file) resides is active

before any application opens to clients
before any TP initialization processing that involves pseudo- or real database communication
before any Coordinator daemons are started

Prior to beginning with the installation, allocate a database number and file number for the configuration file that is shared by Adabas System Coordinator, Adabas Fastpath, Adabas Vista, and Adabas Transaction Manager.

Notes:

If an (optional) alternate configuration file is to be used, this must be allocated in a different database to the primary file.
It is your responsibility to ensure the alternate file has the same configuration content as the primary file.
Both the primary and the alternate configuration files must be available at startup and shutdown of Coordinator daemons.

Adabas System Coordinator Daemon

Prior to beginning with the installation, a Node ID for each Adabas System Coordinator daemon must be allocated.

Using System Coordinator With Version 8 Link Modules

System Coordinator Version 8 is compatible with Version 7 and Version 8 link modules. For Version 7, System Coordinator is activated by linking a stub module with the link module. For Version 8, the Coordinator stub module must be linked with the LNKGBLS module. The LNKGBLS module must be re-assembled, specifying the parameter COR=YES in the LGBLSET macro. The Coordinator will not activate if the stub is incorrectly linked.

Note:
The LNKGBLS module is not used in BS2000 systems. The Coordinator stub is linked with ADALNK.

Note:
Adabas client-based products are not compatible with the Adabas DBID/SVC routing feature. If you wish to use multiple SVCs in the same client job you should implement the COR versioning feature instead.

Use of Unmodified ADALNK

The Coordinator client component is activated by binding a stub module to the Client Adabas Link Module (ADALNK or other). This stub module is for use in client environments only. In previous versions it has been a documented restriction that the ADALNK module used by the COR daemon and Adabas servers must not contain the COR client stub. This remains the recommended procedure. However, in this version COR will auto-detect and bypass invalid client stub invocation in the COR daemon and Adabas servers.

You must still ensure that you use an unmodified ADALNK in Adabas utility jobs.

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT