Run and monitor the synchronization request - Connect_CDC - connect_cdc_mimix_share - aws_mainframe_modernization_service - 6.x

Connect CDC Getting Started Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
ft:locale
en-US
Product name
Connect CDC
ft:title
Connect CDC Getting Started Guide
Copyright
2025
First publish date
2003
ft:lastEdition
2026-02-25
ft:lastPublication
2026-02-25T19:01:02.274000
L1_Product_Gateway
Integrate
L2_Product_Segment
Data Integration
L3_Product_Brand
Precisely Connect
L4_Investment_Segment
Application Data Integration
L5_Product_Group
ADI - Connect
L6_Product_Name
Connect CDC

Running and monitoring a Synchronization request require the same steps as described for a Copy or a Replication request (see Define the request and Define a replication request in Connect CDC Director for more information).

Note: These sections contain basic information about Connect CDC MonCon. You can also use Connect CDC Console (a command-line UI). For more information, see the Advanced User Guide.
  1. Return to Connect CDC MonCon, or restart it (see Start Connect CDC MonCon).

  2. Select View>Model Update to reference the new version of your model. Connect CDC MonCon ensures that all the product components reference this updated version.

  3. Start the Synchronization request using one of the following start options:

    • Start checks if the request has successfully completed the copy phase. If it has, Synchronization starts replication of changed-data. If it has not, Synchronization starts copying the source tables.

    • Start from copy displays a confirmation dialog asking if you want to copy all tables in the request.

    Note: Change capture options, introduced in Enable/disable capture, are also available on Synchronization requests. 
  4. Monitor the messages tracking the processing of the request on the Command Trace and Alert Messages tabs.

  5. Refresh the Statistics window.

  6. Verify that the values for the transaction rows retrieved and sent are as anticipated and match those for the rows applied.