The Replication Agent for DB2 UDB is a mainframe z/OS application. It consist of two tasks that run simultaneously in a single z/OS address space:
Sybase Log Extract – continuously scans the IBM DB2 Universal Database active and archive logs for data-changing operations on primary tables.
LTM for MVS – receives replicated transactions from Sybase Log Extract, converts them to Log Transfer Language (LTL), and then sends them to the primary Replication Server.
One Replication Agent for DB2 UDB started task is required for each IBM DB2 Universal Database log from which transactions will be replicated.
All Replication Agent installation and configuration issues are described in the Replication Agent for DB2 UDB Installation Guide. However, the following items may need further attention in a heterogeneous replication system:
All configuration parameter values in the LTM for MVS configuration file are case sensitive. Be careful when specifying the values of the RS_source_ds and RS_source_db parameters, as the Replication Server is also case sensitive. If the same case is not used in both Replication Agent and Replication Server parameters, the connection does not succeed.
The LTM for MVS LTM_process_maint_uid_trans configuration parameter controls whether the Replication Agent sends transactions performed by the Maintenance User to the primary Replication Server. The Maintenance User ID is defined in the Replication Server create connection command for the primary database.
In a bidirectional replication environment (replicating both into and out of the same IBM DB2 Universal Database region), the value of the LTM_process_maint_uid_trans parameter should be set to N. If it is not, transactions replicated to another site could return to be applied at the originating site, creating an endless loop.
