View continuous replication summary

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

As a last step you review and confirm all settings and configurations of the continuous replication pipeline. This includes verifying connections, examining source data selections, and ensuring accurate field mappings. Once satisfied with the configuration summary, you can create and activate the continuous replication pipeline, completing the setup process.

Note: The screen is displayed for a user with Designer and Operator permission.
Table 1.
Stage Configuration Changes Commit the configuration changes for all replication pipelines to the runtime environments.
Note: Click Validate Configuration to validate the selected configuration before the replication pipeline is staged or committed.
Make Configuration Changes Active Deploy the configuration changes for all replication pipelines in the runtime environments. Replication will continue for any existing replication pipelines while the configuration changes are made active.

Download JCL File - Displayed only for projects that have one or more pipelines that are using a Db2 for z/OS type data connection and the Share model is out of sync with the mainframe model.

Start Replication Pipeline If the pipeline has not been run previously, you can starts the replication pipeline.
Note: Only displayed when the user has both Designer and Operator roles. Only operators can start replication.

Download JCL files

When your replication project includes one or more pipelines that use a Db2 for z/OS JDBC data connection, each time you deploy the project you must first download the latest Job Control Language (JCL) files which are used to run and manage processes on z/OS systems. After you download the files, each file must be copied to and run on the z/OS server associated with the agent referenced in the file name. This ensures the latest capture configuration is active on those servers.

When you download the JCL files, one JCL file is created for each agent associated with your project. By default, the syntax for a JCL file name is ProjectName_CaptureServerName_CapturePort_AgentName_CommittedVersion.jcl. For example, MyProject_z/os.mycompany.com_2638_MyAgent_5.jcl. The JCL files are added to a single zip file. By default, the syntax for the zip file name is ProjectName-(CommittedVersion)-jcls.zip and it will be downloaded to a location you specify. For example, MyProject-10-jcls.zip.
Note: The file name for a project that has not yet been committed will always be appended with a version number of 1.

After you download the zip file, copy the JCL files to the z/OS servers, run the JCL files, and deploy the project.