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.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange Change Data Capture Introduction
  3. Part 2: CDC Components Configuration and Management
  4. Part 3: CDC Sources Configuration and Management
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: CDC for z/OS Troubleshooting
  8. Appendix B: DTL__CAPXTIMESTAMP Time Stamps

CDC Guide for z/OS

CDC Guide for z/OS

Back Next

Commands for Controlling DB2 ECCR Processing

Commands for Controlling DB2 ECCR Processing

You can control the DB2 ECCR either by issuing MVS MODIFY commands to the ECCR. You can also change configuration statements in the REPL2OPT DD file and then issue the REFRESH command or restart the ECCR.
The following table summarizes the MVS MODIFY commands that you can use to control the DB2 ECCR:
Command
Description
DISPLAY
Prints statistics reports on ECCR activity.
QUIESCE
Stops the DB2 ECCR after all in-flight UOWs for the ECCR complete and the ECCR sends the change records to the PowerExchange Logger.
REFRESH
Refreshes the ECCR after you update configuration statements in the REPDB2OP member in the RUNLIB library or after you add, edit, or delete capture registrations for DB2 source tables. The refresh operation activates the new DB2 ECCR options and registration changes for change data capture. You can refresh the DB2 ECCR only while it is active.
The REFRESH command ignores any changes that you make to the CA NAME statement in the REPL2CTL data set and to the IFI306 and START statements in the REPL2OPT data set. The REFRESH command is equivalent to stopping the DB2 ECCR and then restarting it with the START WARM statement.
URID
Lists the DB2 URIDs for the DB2 subsystem or data-sharing group to which the DB2 for z/OS ECCR is connected.
Other DB2 ECCR MODIFY command are primarily for use by Informatica Global Customer Support. For more information, see the
PowerExchange Command Reference
.
You can also use the MVS START and STOP commands to start and stop the ECCR started task or job. The STOP command stops the DB2 ECCR immediately without waiting for in-flight UOWs to complete or for change records to be sent to the PowerExchange Logger. Informatica recommends that you use the QUIESCE command instead.
0 COMMENTS
We’d like to hear from you!