Be sure your system meets the requirements described in System Requirements.
To install Event Replicator for Adabas on BS2000 systems, complete the steps described in this document.
Step 5. (Optional) Load the Adabas Event Replicator Subsystem Application Into Natural
Step 8. (Optional) Assign Permanent Files to BS2000 Link Names
Step 10. Set up Subtasking with EntireX Broker Access (Optional)
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.MOD.
Create a database for use in the Event Replicator Server startup job. See 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.
Note:
User application files should not be loaded on the
Event Replicator Server.
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, read Event Replicator Server Initialization Parameters.
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:
Load a Replicator system file on the Event Replicator Server (defined in the previous step) using the ADALOD utility. A sample ADALOD utility job is provided in member ADALODRP of the ARFvrs.SRC 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 (file) 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).
In Adabas, set the SUBMPSZ (say 50,000,000 ) parameter large enough to accommodate the LRPL parameter above.
Set ADARUN parameter LU to 167,000 or greater.
If you are using webMethods Broker and NET communication, make sure that the DEFAULTS=NET section of the file identified by the ETBFILE link parameter file sets the IUBL parameter to the same size as the LU ADARUN parameter setting.
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.
Set ADARUN parameter CMDQMODE to "ABOVE". Large NC and NAB values are also required here in the Entire Net-Work and Event Replicator Server. These need to be placed above the 16MB area where there is more space.
Notes:
If the default router IDTNAME ADABAS5B is not being used, assign a permanent file to the DDLNKPAR link name as follows:
/SET-FILE-LINK DDLNKPAR,filename
The file identified by the DDLNKPAR link name should contain an ADALNK IDTNAME parameter setting (where xxxxx is the desired suffix):
ADALNK IDTNAME=ADAxxxxx
Where there is no access to the BS2000 console, the Adabas nucleus and Event Replicator Server jobs should assign permanent files to the following link names:
/SET-FILE-LINK DDPRINT,ddprint_permanent_filename
/SET-FILE-LINK DDDRUCK,dddruck_permanent_filename
These files can be accessed when the jobs are running by specifying:
SHOW-FILE ddprint/dddruck_permanent_filename
This will not show the actual file data until the next file block is filled and flushed.
Run the Event Replicator Server job you set up in Step 5.
If an output queue with ETBROKERNAME=BROKER or an input queue with IQTYPE=ETBBROKER has been defined (read Event Replicator Initialization Parameters), then the BS2000 Event Replicator Server will run subtasks. In BS2000 environment, these are separate jobs that communicate via common memory.
The number of output subtasks is determined by the SUBTASKS parameter setting. The number of input subtasks is determined by the number of IQUEUE definitions.
If all is correctly defined, this will show:
ADAF90 00073 001 output subtasks to be attached ADAI5X 00073 Subtask ADABSP started with TSN 7245 ADAF93 00073 001 input subtasks to be attached ADAI5X 00073 Subtask ADABSP started with TSN 7246 ADAF92 00073 Output subtasks have been initialized ADAF92 00073 Input subtasks have been initialized
Here, 73 is the node number of the Event Replicator Server, 7245 is the job number of the output subtask, and 7246 is that of the input subtask. The job name is always ADABSP (this can be seen by the SHOW-USER-STATUS command).
If there is a problem with the definitions or connections, the following may occur:
ADAF90 00073 001 output subtasks to be attached ADAI5X 00073 Subtask ADABSP started with TSN 7245 ADAF93 00073 001 input subtasks to be attached ADAI5X 00073 Subtask ADABSP started with TSN 7246 ADAI68 ADAIO2 DISABLING SUBROUTINE 7246 ADABSP ADAF95 00073 All input subtasks could not be initialized
If this happens, review the output protocol of the subtask. This is a sequential file with the naming convention:
L.O.<replicator-nucleus-task-number>.ADABSP##.<timestamp>
Within this file, a message in the following format may be seen:
ADAF87 00073 AMI R=CONNECT Q=ETB0901: RC=008/060/F0F2F1F5/F0F1F4F8
In this example, the communication type is NET to a Broker with a Broker ID of "901". The last two fields can be interpreted as 0215/0148. These are the EntireX Broker error message code number and message number (for more information, refer to the EntireX Broker Messages and Codes).
Note:
When an input subtask failure occurs, attempts are made to
reconnect as many times as defined by IQRETRYCOUNT and intervals of
IQRETRYINTERVAL.
The subtask jobs are automatically terminated when the Event Replicator Server terminates.
The ARFvrs.ZAPS library contains the element ZAPVvrs(J). This contains a list of Adabas released zaps that need to be applied for the Event Replicator to work. Please ensure that these zaps have been applied before starting the Event Replicator.
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).