Chapter 4. Peer-to-peer Q replication on z/OS platforms 361
“Stop the Q Apply program that is applying data for the Q subscription in
error” affects latency by introducing a delay; however, it permits correction
without having to reload/resynch.
Click Next to specify how the target tables should be loaded in Figure 4-59.
Figure 4-59 How should target tables be loaded
We chose the Manual option for this set of tables, indicating that we would be
responsible for synchronizing the data in the target table with that of the source
tables and sending a LOADDONE signal to the source Q Capture program when
the load was completed. We selected the Start all Q subscriptions
automatically option target tables. We also selected DT11 to be the source for
the initial load, as shown in Figure 4-59.
Click Next to review the subscriptions defined.
362 WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios
Figure 4-60 Review and complete Q subscriptions
Figure 4-60 is displayed while both z/OS databases are checked for accuracy of
the replication request, and verified that the tables can be replicated. At the end
of this Figure 4-61 is displayed showing the 46 subscriptions—two for each of the
364 WebSphere Information Integrator Q Replication: Fast Track Implementation Scenarios
Figure 4-62 Create Q Subscriptions - Summary
Review the summary in Figure 4-62 and click Finish to generate the scripts for
creating the various objects on the two servers, as shown in Figure 4-63.
Click the Back button to go back and correct any errors.