DB2 UDB Primary Database Configuration

Replication Agent can run against a single DB2 subsystem, or all logs in a DB2 data-sharing group. LTMCFG parameters describe the DB2 environment for Replication Agent for DB2 UDB (DataSharingOption, DataSharing Member, Log-identifier, and BSDS.)

The Replication Agent for DB2 UDB is a mainframe z/OS application consisting of two tasks that run simultaneously in a single z/OS address space:

Sybase Log Extract – continuously scans the DB2 UDB active and archive logs for data-changing operations on primary tables.
Replication Agent for DB2 UDB for z/OS – receives replicated transactions from Sybase Log Extract, converts them to Log Transfer Language (LTL), and sends them to the primary Replication Server.

When the DataSharingOption is Multi, Replication Agent for DB2 UDB refers to the Boot Strap Dataset (BSDS) parameter to identify the BSDS for each DB2 member in the data-sharing group, and displays the position of the Replication Agent for DB2 UDB and the DB2 log for each member of the group.

All Replication Agent installation and configuration issues are described in the Replication Agent for DB2 UDB Installation Guide. However, in a heterogeneous replication system:

The values of the rs_source_ds and rs_source_db parameters are case-sensitive. If you do not use same case in both Replication Agent and Replication Server parameters, the connection fails.
The Replication Agent for DB2 UDB for z/OS LTM_process_maint_uid_trans configuration parameter controls whether the Replication Agent sends transactions executed by the maintenance user to the primary Replication Server.

In a bidirectional replication environment (replicating both into and out of the same DB2 UDB region), set the value of the LTM_process_maint_uid_trans parameter should be set to N. If you do not, transactions replicated to another site may return to be applied at the originating site, creating an endless loop.