CDC Guide for z/OS

10.5
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

Change Capture from a Single DB2 Subsystem with Multiple Capture Environments

If you need to capture changes from separate capture environments on the same DB2 subsystem, each environment with its unique DB2 ECCR, review the following considerations:

Each DB2 ECCR execution must have its own unique parameter files. These files are specified in the REPL2CTL and REPL2OPT DD statements in the ECCR JCL.

Each DB2 ECCR must have its own set of DB2 capture directory tables.

Each DB2 ECCR must have its own unique qualifier and plan name in the BIND for the packages and plans.

The ECCR name that you specify in the CA NAME statement in the REPL2CTL DD data set must be unique for each DB2 ECCR and across the z/OS image and a sysplex.

DB2 registrations contain either the DB2 subsystem ID (SSID) or group attachment name. To allow registrations to be divided among multiple capture environments, each DB2 ECCR must have its own PowerExchange Listener, Agent, and Logger tasks.

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

Change Capture from a Single DB2 Subsystem with Multiple Capture Environments

Change Capture from a Single DB2 Subsystem with Multiple Capture Environments