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

Files That PowerExchange Condense Uses

Files That PowerExchange Condense Uses

PowerExchange Condense uses multiple files to perform its processing.
Some files are allocated at installation, and other files are created dynamically by PowerExchange Condense. Also, some files are re-used within a process, whereas other files are allocated, written to, and passed to other change data capture processes.
The following table lists the files that PowerExchange Condense uses:
File Name
Library
Description
CCT
datalib
Contains information about capture registrations. This file is used by the PowerExchange Listener and PowerExchange Condense. The PowerExchange Listener job opens the file in read/write mode, whereas PowerExchange Condense only reads the file.
CDCT
datalib
Contains information about the condense files for extraction processing. PowerExchange Condense opens the file in read/write mode to update CDCT information. After a warm start, PowerExchange Condense synchronizes the CDCT file with the current checkpoint file. The PowerExchange Listener job reads the CDCT information on behalf of data extraction processes to find the condense files to process.
CDEP
datalib
Contains information about each extraction process that has run to provide an audit trail. The PowerExchange Listener uses this file to provide output to extraction processes and input to application groups in PowerExchange Navigator.
CFG
datalib
Contains the DBMOVER member with the PowerExchange configuration statements. Some of these statements are applicable to PowerExchange Condense.
CFGCOND
condlib
Contains the CAPTPARM member with the PowerExchange Condense parameters.
CHKPTV
nn
condlib
CHKPTV
nn
checkpoint files are dynamically created and deleted by PowerExchange Condense based on parameters in the CAPTPARM member. The primary purpose of the checkpoint files is to provide the restart and sequence tokens, which indicate the log position from which to resume reading uncommitted UOWs and the the position at which to release data records that have not yet been processed. The secondary purpose of the checkpoint files is to reconstruct the CDCT file if you need to resume processing from an older point in time.
Informatica recommends the use of nine checkpoint files so that you are likely to have enough checkpoint files from which to reconstruct the CDCT file.
DTLMSG
dtllib
Contains prototype strings for PowerExchange messages.
Full condense file
condlib
A condense file that is produced at
condlib
/FULL* if you select Full condense processing.
LICENSE
dtllib
Contains the PowerExchange license key for PowerExchange and the PowerExchange options that you purchase.
LOG
datalib
Contains the PowerExchange message log member, DTLLOG, that includes messages about PowerExchange Condense and PowerExchange Listener processing when alternate logging is
not
enabled.
Because PowerExchange writes a lot of information to this file, you should perform routine maintenance on it to ensure that it does not become too large. Informatica recommends that you use the CLRPFM command to clear the file.
If you enable alternate logging by specifying the TRACING statement in the DBMOVER member, PowerExchange creates message members in the file named JOB
job_number
in the
datalib
library. The member names have the prefix that is specified in the TRACING statement.
Partial condense file
condlib
A condense file that is produced at
condlib
/PARTIAL after each file switch if you select Part condense processing.

0 COMMENTS

We’d like to hear from you!