Replicating Data to Adabas in Binary Mode

You can use the Event Replicator Target Adapter to replicate data to an Adabas LUW target using raw binary data sent from the Event Replicator on the mainframe. The Event Replicator Target Adapter uses Entire Net-Work Server to connect to an Adabas LUW target and Adabas direct calls to process the replicated transactions..

This document describes how to set up the Adabas target in the Event Replicator Target Adapter. It covers the following topics:

Requirements

  • Direct replication in binary mode requires Event Replicator for Adabas Version 3.8 SP1 (or higher) on the mainframe with the following zaps applied:

    • AZ381005

    • AZ381007

    • AZ381013

  • The Destination used in the Event Replicator Subscription must use the Destination Class Parameter (DCLASSPARM) "SAGTRGB". For details, please refer to the Event Replicator for Adabas documentation.

  • Your target database must be accessed via an Entire Net-Work node (kernel) which registers the database for client access.

  • The Entire Net-Work node must register the target with a Software AG Directory Server. The target adapter functions as a Directory Server client to retrieve the appropriate access entry for the target database ID; it then uses the communication path to the appropriate Entire Net-Work node provided by the Directory Server. For details on configuring Entire Net-Work to register Adabas databases, see the Entire Net-Work documentation.

Adabas-Specific Notes

Adabas (Binary) as Targets for Target Adapter - Use and Limitations

In the current implementation, there are certain restrictions and limitations to using the Adabas (Binary) target for replication:

  • Entire Net-Work and a Directory Server must be used for the Target Adapter to access the Adabas LUW target, even if the target database and Target Adapter are installed on the same system. There is currently no way to provide the Target Adapter a direct path to the target, e.g. an ADATCP port or direct path to an Entire Net-Work Server port.

  • Event Replicator Target Adapter Administration is used to configure the source-to-target mapping to be used in replication to an Adabas (Binary) target. It is possible to map multiple source DBIDs and files to multiple target files in a single mapping. For examples and an explanation of how the mapping is configured, refer to Event Replicator for Adabas > Event Replicator Target Adapter > Event Replicator Target Adapter Administration > Using Event Replicator Target Adapter Administration > Maintaining Adabas Target Definitions.

  • Event Replicator Target Adapter has the ability to create the configured target file in the target database if it does not exist when a schema is received and replicated. How this is done depends on the method used to initially create and populate the target file. The following methods are available:

    • Use the ADALOD utility on the mainframe. Use of this method requires the following:

      1. A parameter setting of DREPLICATEUTI=Y on the Event Replicator Destination definition used.

      2. The ADALOD parameter RPLLOAD=FILE in the ADALOD job on the mainframe.

      When this method is invoked using the specified parameters and the mainframe database is loaded, creation of the configured target file is triggered including the FCB/FDT of the source file and the target file populated as well. Using this approach, the resulting target file is an exact replica of the source. For more information and details on using the ADALOD utility, see the Adabas for Mainframes documentation.

    • Using SYSRPTR on the mainframe, perform an Initial State of the file to be replicated (in SYSRPTR, Administrative Functions --> Perform Initial State). This method may also be used to create a target file, however the resulting FDT of the created file will not be identical to the FDT of the mainframe source. The extended field attributes of the created fields and super-/sub-descriptors specified in the source FDT will be missing. If the user wishes to use this method and requires these extended attributes on the target file’s fields, the file must be pre-loaded with an FDT identical to the one used on the mainframe source file. Refer to the Adabas LUW documentation for information on how to load an FDT for a new file.

  • In all replication cases except the ADALOD scenario described above, the actual data replicated to the target Adabas file is controlled by the GFB/GFFT specified in the Event Replicator Subscription that controls replication. Source fields missing from or defined differently than the source field will be replicated as per the active GFB. For example, if field AE in the source is defined as AA,20,A, but defined in the Subscription File Parameters GFB as AA,1,A, only the first byte of the field will be replicated. The user should take care that the GFB/GFFT defined in the Subscription describes the data desired for replication. For best results, when defining and generating the GFB/GFFT, we recommend use of the Event Replicator Target Adapter Data Mapping Tool to create optimized GFBs for use in your replication scenario.

  • For a listing of certain restrictions and limitations on the use of the Adabas (Binary) Target feature, refer to the Release Notes and product and fix Readme files.