Table of Contents

Search

  1. Preface
  2. Change Data Capture Introduction
  3. PowerExchange Listener
  4. PowerExchange Condense
  5. DB2 for i5/OS Change Data Capture
  6. Remote Logging of Data
  7. Introduction to Change Data Extraction
  8. Extracting Change Data
  9. Monitoring CDC Sessions
  10. Managing Change Data Extractions
  11. Tuning CDC Sessions
  12. Appendix A: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for i5/OS

CDC Guide for i5/OS

Customizing the DBMOVER Configuration Member for Remote Journal Use

Customizing the DBMOVER Configuration Member for Remote Journal Use

You must define some DBMOVER statements to enable PowerExchange to capture change data from remote journal receivers and to read metadata from the DB2 source tables.
On the remote i5/OS system that contains the remote journal receivers, configure the following DBMOVER statements in addition to those that are normally required for CDC:
  • In the JOURNAL parameter in the AS4J CAPI_CONNECTION statement, enter the JRN=
    library
    /
    journal_name
    subparameter to identify the remote journal to override. The journal contains journal entries for the registered source tables.
  • Optional. Edit the RMTSYSNAME and RMTRDBDIRE statements to override the host name and database name that the CRTPWXENV command sets during installation:
    • In the RMTSYSNAME statement, enter the host name of the system where the Db2 source tables reside.
    • In the RMTRDBDIRE statement, enter the name of the Db2 database that contain the Db2 source tables.
On the Windows system where the PowerExchange Navigator runs, define a NODE statement in the dbmover.cfg file that points to the remote system where the remote journal receivers reside. This statement enables the PowerExchange client on Windows to connect to the PowerExchange Listener on the remote system. You do not need to specify an AS4J CAPI_CONNECTION statement in the dbmover.cfg file on the Windows system.

0 COMMENTS

We’d like to hear from you!