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

Using Multiple Journals with PowerExchange Condense

Using Multiple Journals with PowerExchange Condense

You can configure the PowerExchange change data capture environment to capture changes from more than one journal. To do this, you need to establish a PowerExchange Condense, or CONDLIB, library for each journal that you want to condense.
If you have multiple journals, or you might have them in the future, copy the supplied CONDLIB as a template before you customize or use it. Each CONDLIB library has its own CAPTPARM member that specifies the journal to be condensed.
A single PowerExchange Listener can be used for multiple PowerExchange Condense jobs and extractions from multiple journals.
Within each CONDLIB library, you must customize the CAPTPARM member to point to the appropriate journal and CONDLIB library.
For example, to run PowerExchange Condense for the first journal, configure the following parameters in
condlib
/CFGCOND(CAPTPARM):
DBID=
instance1
(This uses the journal in DBMOVER.) CHKPT_BASENAME=
condlib
/CHKPT COND_DIR=
condlib
To run PowerExchange Condense for a second journal, configure the following parameters in a second
condlib
called
condlib2
/CFGCOND(CAPTPARM):
DBID=
instance2
JRNL=
library
/
journal2
(The journal override.) REG=(
reg1
) REG=(
reg2
) REG=(
reg3
,DB=
library
/
file
) CHKPT_BASENAME=
condlib2
/CHKPT COND_DIR=
condlib2
To run PowerExchange Condense for a third journal, configure the following parameters in a second
condlib
called
condlib3
/CFGCOND(CAPTPARM):
DBID=
instance3
JRNL=
library
/
journal3
(The journal override.) CHKPT_BASENAME=
condlib3
/CHKPT COND_DIR=
condlib3
Capture registrations can be specified in either the CAPTPARM member or the DBMOVER configuration member but not in both members. If no capture registrations are specified, all capture registrations that specify a Condense Type other than None are included.

0 COMMENTS

We’d like to hear from you!