Be sure your system meets the requirements described in System Requirements.

To install Event Replicator for Adabas on z/OS systems, complete the steps described in this document.

• Step 1. Install the Replication Load Modules

• Step 2. Apply Necessary Zaps

• Step 3. (Optional) Create the ADAMQS Load Module for WebSphere MQ Support

• Step 4. Create the Event Replicator Server

• Step 5. (Optional) Load a Replicator System File

• Step 6. (Optional) Load an SLOG System File

• Step 7. (Optional) Load the Adabas Event Replicator Subsystem Application Into Natural

• Step 8. Set Up the Event Replicator Server Startup JCL

• Step 9. Start the Event Replicator Server Job

• Step 10. Implement Replication

• Special Considerations for zIIP Support

---

Step 1. Install the Replication Load Modules

Install the replication load modules by concatenating the delivered load library in sequence or copying the modules to the library used for running the Adabas nucleus and utilities. The Replication load modules can be found in ARFvrs.LOAD.

Step 2. Apply Necessary Zaps

Apply any necessary zaps, as described in the $README file on the ARFvrs.MVSZAPS library and in any subsequent ARFvrs.MVSZnnn data sets (if they have been provided).

Step 3. (Optional) Create the ADAMQS Load Module for WebSphere MQ Support

If WebSphere MQ will be used, execute a job for linking ADAMQS. To create the required Event Replicator Server load module called ADAMQS, use JCL similar to this:

//LINK     EXEC PGM=IEWL,PARM='LIST,XREF,REUS,RENT'
//SYSPRINT DD SYSOUT=*
//SYSUT1   DD UNIT=SYSDA,SPACE=(CYL,(3,1))
//ADALIB   DD DISP=SHR,DSN="ADABAS-Event-Replicator-Load-Library"
//MQSLIB   DD DISP=SHR,DSN="MQ-Series-SCSQLOAD-Library"
//SYSLMOD  DD DISP=SHR,DSN="User-Load-Library"
//SYSLIN   DD *
 INCLUDE ADALIB(ADAMQT)
 INCLUDE MQSLIB(CSQBSTUB)
 ENTRY ADAMQS
 NAME  ADAMQS(R)
/*

Step 4. Create the Event Replicator Server

Create a database for use as your Event Replicator Server. Read the ADADEF documentation for the new parameters used when defining an Event Replicator Server.

If you want to perform transaction logging or use TLOG destination definitions, be sure to create and activate a CLOG (command log). For more information, refer to your Adabas DBA Tasks documentation.

Step 5. (Optional) Load a Replicator System File

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 DDKARTE in the Event Replicator Server startup job. For more information about the initialization parameters you can specify in the Event Replicator Server startup job, 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:

1. Use the ADALOD utility. A sample ADALOD utility job is provided in member ADALODRP of the ARFvrs.JOBS data set. 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.

2. 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.

Step 6. (Optional) Load an SLOG System File

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.

Step 7. (Optional) Load the Adabas Event Replicator Subsystem Application Into Natural

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.

Step 8. Set Up the Event Replicator Server Startup JCL

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 .

1. 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.

2. 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).

3. Set ADARUN parameter LU to 167,000 or greater.

4. 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).

5. Set ADARUN parameter NT to a value greater than or equal to 15.

Step 9. Start the Event Replicator Server Job

Run the Event Replicator Server job you set up in the previous step.

Step 10. Implement Replication

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).

Special Considerations for zIIP Support

This section contains the following topics:

• Prerequisites

• Libraries

• License

• Adabas Online System

Prerequisites

Prerequisite for the zIIP support in the Event Replicator for Adabas is a z13 or z14 mainframe with one or more zIIP engines, running z/OS 2.1 or above. The Event Replicator Server needs one zIIP engine to perform effectively.

For zIIP support, the Event Replicator Server must be based either on Adabas for zIIP 8.3 SP5 (AZP835.LOAD library), on Adabas for zIIP 8.4 SP3 or on Adabas Version 8.5 SP1.

If Adabas for zIIP 8.3 SP5 is used for the Event Replicator Server, zap AN835065 must be applied.

For online administration of the zIIP-related functions and statistics of the Event Replicator Server, the version of the Adabas Online System provided with Adabas for zIIP 8.3 SP5, Adabas for zIIP 8.4 SP3 or Adabas Version 8.5 SP1 must be installed (AZP835.INPL or AZP843.INPL or ADA851.INPL, respectively).

If one or more destinations defined in the Event Replicator Server use EntireX Broker as the messaging system (DTYPE=ETBROKER), EntireX Broker version 10.1 patch level 11 or higher must be used.

Libraries

For the zIIP license check in Event Replicator for Adabas (see License below), use the Mainframe License Check version 1.3.3 from the following library:

• MLC133.LOAD

License

An Event Replicator Server that is to run with zIIP support requires an associated license file (AZPRP) in addition to the Adabas license file. If the AZPRP license is not provided or erroneous, the Event Replicator Server will run, but without zIIP support (ZIIP=NO).

The AZPRP license can be transferred to the mainframe in the same way as the Adabas license. The license can be made available to the Event Replicator Server as a load module with the name ‘AZPRPLIC’. This is similar to the handling of the Adabas license load module ADALIC described in the Adabas documentation under Installing Adabas for z/OS.

Alternatively or in addition, the license file can be referred to by a ‘DDLAZPRP’ DD statement in the nucleus job/started task. This is a fallback for the case that the AZPRPLIC module cannot be loaded.

Adabas Online System

If either

• the ADA851.INPL dataset for Adabas 8.5.SP1 or

• the AZP843.INPL dataset of Adabas for zIIP 8.4 SP3 or

• the AZP835.INPL of Adabas for zIIP 8.3 SP5 is installed,

it will be possible to use Adabas Online System (AOS) to review the zIIP statistics of the Event Replicator Server and to view and modify the ZIIP parameter, even if you do not have an AOS product license.