Note
As of Syniti Replicate version 10.7.x, the Log Reader API is deprecated.
Enable Transactional Replication wizard or the Manage Transactional Log Settings dialog
The information below explains how to configure the transactional replication settings for IBM Db2 for i in the Enable Transactional Replication wizard or the Transactional Log Settings dialog available from the Transactional Setup > Manage option on the connection in the Metadata Explorer.
When replicating from IBM Db2 for i using mirroring or synchronization, two transactional modes are available: Log Reader and Log Server Agent.
For all three modes, you first need to set up a library on your Db2 system. This step sets up the library by transferring a savf file to the Db2 server and creating the DBMOTOLIB library (or a library name of your choosing). You can also perform this procedure manually for more complete control over operations or in case the automatic process does not work.
Library Name
The library name, DBMOTOLIB, is supplied. This field can be modified to supply a different library name. This is the name of the library that will be created on the Db2 system. It can be useful to change the default library name when, for example, you have two Syniti Replicate installations using the same database server, and you wish to keep separate libraries for each installation.
DBMOTOLIB Contents
[file] DBMLIBVER containing one single record with the library version;
[program] JRNSQNM used to retrieve the last transaction id in the journal;
The DBMOTOLIB library, if set also as A temporary library, is used to contain all temporary files created by the Syniti Replicate during transactional replications that use IBM i/iSeries/AS400 as source server (and target, if in synchronization).
Savf File
The location of the savf file in the installation directory. This file is run to create a stored procedure on the Db2 system, and the version of the file should match the operating system that you are using. Modify this path to point to a different file version if needed, or if you move the savf file to a different location. If you are using operating system V5R4 or above, and choose either the DBMLIB54.SAVF file or the DBMLIBAPI61.SAVF file, a checkbox is displayed to allow you to install the procedure JRNSQMAPI. The box should be checked if you are planning to create more than 30 replications from a Db2 for i source database.
Verify (appears only in the Transactional Log Settings dialog)
Click Verify first to see if the library that Syniti Replicatewill use (specified in Library Name) is already installed on the server. Depending on the results of this operation, the Install button will become active. Click Install to create the library on the Db2 system. To later remove the library from the server, use the Disable Transactional Replication wizard available from the Transactional Setup > Disable option on the connection in the Metadata Explorer.
FTP Status
This area reports progress after you have entered all the information above and clicked Install.
Errors during Installation
The FTP status area may report errors when attempting to restore the DBMOTOLIB library. Errors usually involve:
A user ID with read-only permissions on the Db2 server or no QSECOFR privileges. This can be addressed by running the process again with a login that has write permissions and QSECOFR privileges.
Library or Savefile are already present on the Db2 server, and cannot be overwritten or deleted. This can usually be addressed by using a login that has privileges to delete/overwrite existing files.
In general, if errors occur during the process of automatically restoring the .savf file, you can restore the DBMOTOLIB library manually.
Troubleshooting
If you encounter problems while trying to create DBMOTOLIB during the setup process for IBM i/iSeries/AS400 replications, check:
The IBM i/iSeries/AS400 user ID has an IBM i/iSeries/AS400 login with write permissions and QSECOFR privileges.
Library or Savefile are already present on the iSeries/AS400, and cannot be overwritten or deleted. This can usually be addressed by using an IBM i/iSeries/AS400 login that has privileges to delete/overwrite existing files.
If object JRNSQNM has really been created in DBMOTOLIB, you can continue with setting up connections and creating replications.
If object JRNSQNM has not been created, you should delete DBMOTOLIB, and create it again from Syniti Replicate.
Tracking Journal/Receiver and Transaction Progress
For replications with IBM Db2 for i/iSeries/AS400 as a source, you can track journal, receiver and transaction information as the replication progresses:
Open the Management Center.
In the tree, expand the metadata for your replication.
From the tabs on the right side of the Management Center, choose the Replication Monitor.
Select the replication for which you want to view journal, receiver and transaction information.
The lower pane in the Replication Monitor displays the following information:
Transaction Name
Transaction Timestamp
Journal Library
Journal Name
Receiver Library
Receiver Name
This information is updated dynamically.
You can also use the Replication Properties dialog box to view current journal, receiver, and transaction information. However, information in the Replication Properties dialog box is not updated dynamically.