Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5.2
  • All Products

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

Back Next

Availability of Journal Receivers for DB2 CDC

Availability of Journal Receivers for DB2 CDC

PowerExchange extracts change data for DB2 tables registered for capture by reading journal entries from journal receivers. On busy systems, journal receivers can use a lot of disk storage space and need to be deleted at regular intervals.
Ensure that the journal receivers that are required for change data extraction are available to PowerExchange for read processing. Do not delete a journal receiver until the change data has been read from it and the restart tokens for the CDC sessions or PowerExchange Condense jobs no longer reference the receiver.
To control the deletion of journal receivers, you can use the CRTJRN (Create Journal) or CHGJRN (Change Journal) command to set the MNGRCV (Manage Receivers) and DLTRCV (Delete Receivers) attributes for the journals that are associated with the journal receivers. Informatica recommends the following settings:
  • MNGRCV(*SYSTEM)
  • DLTRCV(*NO)
    If you specify DLTRCV(*YES), the journal receivers might be deleted during an IPL of the i5/OS server. In this case, PowerExchange CDC processing loses the entry that corresponds to the restart token.
Also, PowerExchange provides the following configuration options in the DBMOVER member in the CFG file to lock a journal receiver that it is processing and to notify you when that processing is complete:
  • AS4JRNEXIT
    . Use this journal exit parameter on the AS4J CAPI_CONNECTION statement to prevent deletion of journal receivers from which PowerExchange is reading change data for DB2 tables registered for capture.
  • AS400EVENTMSGQ
    . Use this parameter to specify a message queue to which to write the following messages related to journal processing:
    • If you specify AS4JRNEXIT=Y on the AS4J CAPI_CONNECTION statement, PowerExchange writes message DTL3001 to the message queue when PowerExchange finishes extracting change data from a journal receiver.
    • If you specify ALWCLRPFM=Y on the AS4J CAPI_CONNECTION statement, PowerExchange writes message DTL3002 to the message queue if a journal entry for a CLRPFM command is encountered. PowerExchange cannot replicate changes that result from a CLRPFM command.
0 COMMENTS
We’d like to hear from you!