Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange
  3. DBMOVER Configuration File
  4. Netport Jobs
  5. PowerExchange Message Logs and Destination Overrides
  6. SMF Statistics Logging
  7. PowerExchange Security
  8. Secure Sockets Layer Support
  9. PowerExchange Alternative Network Security
  10. PowerExchange Nonrelational SQL
  11. PowerExchange Globalization
  12. Using the PowerExchange ODBC Drivers
  13. PowerExchange Datatypes and Conversion Matrix
  14. DTL__CAPXTIMESTAMP Time Stamps
  15. PowerExchange Glossary

Source-Specific CAPI_CONNECTION Statements

Source-Specific CAPI_CONNECTION Statements

All PowerExchange CDC systems require CAPI_CONNECTION statements for capture and extraction processing.
You define these statements in the DBMOVER configuration file. The types of CAPI_CONNECTION statements that you define vary by source type and system.
The following table identifies the required and optional CAPI_CONNECTION statements types by operating system:
Source System
CAPI_CONNECTION Types
All z/OS sources
  • LRAP CAPI_CONNECTION for the Log Read API that extracts change data from PowerExchange Logger for z/OS log files (Required)
  • UOWC CAPI_CONNECTION for the UOW Cleanser (Required)
DB2 for i5/OS
  • AS4J CAPI_CONNECTION for the journal reader that extracts change data from DB2 journals (Required)
  • UOWC CAPI_CONNECTION for the UOW Cleanser (Required)
DB2 for Linux, UNIX, and Windows
  • UDB CAPI_CONNECTION for change extraction from DB2 recovery logs (Required)
  • CAPX CAPI_CONNECTION, if you use continuous extraction mode (Optional)
Microsoft SQL Server
  • MSQL CAPI_CONNECTION for change extraction from Microsoft SQL Server distribution databases (Required)
  • CAPX CAPI_CONNECTION, if you use continuous extraction mode (Optional)
Oracle
  • ORCL CAPI_CONNECTION for change extraction from Oracle redo logs (Required)
  • UOWC CAPI_CONNECTION for the UOW Cleanser (Required)
  • CAPX CAPI_CONNECTION, if you use continuous extraction mode (Optional)