Be sure your system meets the requirements described in System Requirements.
To install Event Replicator for Adabas on z/VSE systems, complete the steps described in this document.
Step 1. Set Up the Event Replicator Server Library and Data Set Definition Procedure
Step 5. (Optional) Load the Adabas Event Replicator Subsystem Application Into Natural
Set up a VSE procedure for the Event Replicator Server by tailoring the ARFPROC.X JCL supplied in the ARFvrs library member.
This procedure defines the libraries and files to be used for the Event Replicator Server.
Tailor and run the ADAFRMR.X and ADADEFR1.X JCL members in the ARFvrs library to define the Event Replicator Server nucleus. For more information about the new ADADEF parameters used when defining an Event Replicator Server, read the ADADEF documentation.
If you want to perform transaction logging or use TLOG destination definitions, be sure to create and activate a CLOG (command log).
Note:
User application files should not be loaded on the
Event Replicator Server.
For more information about transaction logging, read Transaction Logging. For more information about TLOG destination definitions, contact your Software AG customer support representative. Finally, for more information about creating and activating a CLOG, refer to your Adabas DBA Tasks documentation.
To use Event Replicator for Adabas and customize its processing, you must supply various replication definitions. You can maintain these definitions in one of two ways:
You can specify Event Replicator initialization parameters for the replication definitions in SYSIPT in the Event Replicator Server startup job. This is placed behind the ADARUN statements as shown in the sample JCL found in the ADANUCA1.X member of the ARFvrs library. For more information about the initialization parameters you can specify, read Event Replicator Server Initialization Parameters. This method of defining replication definitions does not require the use of a Replicator system file because the definitions are read from the initialization parameters in the startup job.
You can maintain your replication definitions in the Replicator system file using the Adabas Event Replicator Subsystem. The Adabas Event Replicator Subsystem is an online interface that must be loaded into Natural before you can use it. Access to the Adabas Event Replicator Subsystem is then available through Natural or from Adabas Online System. For more information, read Using the Adabas Event Replicator Subsystem.
If you determine that you want to maintain your replication definitions in the Replicator system file, you must load the file on the Event Replicator Server.
To load a Replicator system file on the Event Replicator Server:
Use the ADALOD utility. A sample ADALOD utility job is provided in member ADALODRP.X of the ARFvrs library. The only ADALOD utility parameter you should specify in this member is the REPLICATOR parameter. The others are not valid when loading the Replicator system file. See the ADALOD documentation for more information.
Do either of the following in Natural to identify the physical database file to be associated with the system file:
Run a Natural NTLFILE macro for the file. For complete information, refer to your Natural LFILE parameter documentation, found in the Natural for Mainframe documentation on Software AG's Empower web site.
When you start the Adabas Event Replicator Subsystem, be sure to set the Natural LFILE parameter as described in Accessing the Adabas Event Replicator Subsystem. The LFILE parameter can be specified either as a dynamic parameter or inside a Natural SYSPARM profile.
If you intend to use the subscription logging (SLOG) facility, you will need an SLOG system file, which is an Adabas system file on the Event Replicator Server. To set this up, please read Setting Up Subscription Logging. For complete information about the SLOG facility, read Using the Subscription Logging Facility.
If you intend to use the Adabas Event Replicator Subsystem to maintain replication definitions in the Replicator system file (see Step 4), it must be loaded into Natural. To do this, use Natural's INPL utility to load the ARFvrs.INPL data set into the Natural system file libraries.
If you want to use the Adabas Event Replicator Subsystem, access it as described in Accessing the Adabas Event Replicator Subsystem. Be sure also to identify the Replicator system file you want to update as soon as you access the Adabas Event Replicator Subsystem. For information on identifying, loading, and unloading the Replicator system file using the Adabas Event Replicator Subsystem, read Identifying, Loading, and Unloading the Replicator System File.
Set up the startup JCL and parameters for the Event Replicator Server job. Use the JCL for an existing Adabas nucleus as a starting point for creating the Event Replicator Server JCL. For complete information on the ADARUN parameters pertinent to the Event Replicator Server, read Pertinent ADARUN Parameters .
Specify an initial setting for the ADARUN parameter RPLPARMS to "NONE". The RPLPARMS parameter identifies where the replication definitions (initialization parameters) should be read from. A setting of "NONE" allows you to run the Event Replicator Server when you have no definitions set up, providing you an opportunity to specify them.
Set ADARUN parameter LRPL to the size of the Event Replicator Server replication buffer. For performance reasons, Software AG recommends setting LRPL to a relatively large value (e.g. LRPL=40M).
Set ADARUN parameter LU to 167,000 or greater.
Set ADARUN parameter NAB to a value greater than or equal to:
41 * 10 * the-number-of-Adabas-nuclei-sending-data-to-the-Event-Replicator-Server
For example, if one Adabas nucleus will be sending data to the Event Replicator Server, set the NAB parameter greater than or equal to 410 (for example NAB=420).
Set ADARUN parameter NT to a value greater than or equal to 15.
Run the Event Replicator Server job you set up in the previous step.
The previous steps in this section allowed you to install Event Replicator for Adabas, but they did not implement or start replication. How replication is implemented varies by site, but general implementation steps are described in Post-Installation Replication Implementation Steps (All Platforms).