This section covers several operational scenarios likely to be encountered after the initial Capture has been placed into operation, including changes in the scope of data capture and additional use or processing of the captured data by downstream Engines.
One factor to consider when contemplating or implementing changes in an operational configuration is the implementation sequence. In particular processes that will consume captured data must be tested, installed and operational before initiating capture in a production environment. This is critical because the volume of captured data can overwhelm transient storage if the processes that will consume the captured data are not enabled in a timely fashion.
While the examples in this section will generally proceed from capture of changed data to the application at the target by an Engine, it is essential to know what the expected results are before configuring the data capture, for example:
- A new column populated in an new table by an existing engine from a new IMS Segment in an existing DBD; all the changes would be made at the target side where the Engine runs.
- New relational tables to be populated from a new IMS Database maintained by a new IMS transaction, will require configuration changes from one end to the other.
When working through the examples below be prepared to continue from one example to the next when thinking about how to implement your own new scenario.
Finally, implementation of Change Data Capture inevitably leads to questions about the Initial Target Load and the possible need for a full or partial data Refresh. Connect CDC SQData supports that functionality for both the IMS Log Reader and TM Exit captures with multiple options as seen in Initial Target Load and Refresh section below.