Q Replication and Event Publishing

Creating control tables for the Q Capture and Q Apply programs

Before you can publish or replicate data, you must create control tables for a Q Capture program, a Q Apply program, or both. Control tables store information about Q subscriptions and publications, message queues, operational parameters, and user preferences.

Before you begin

The ASNCLP command-line program or Replication Center must be able to connect to the server where you want to create the control tables:
- If you are replicating from DB2® to DB2, then the administration tools must be able to connect to the source and target server.
- If you are replicating from DB2 to a non-DB2 server, then the tools must be able to connect to the source server, the DB2 federated server, and the non-DB2 target server.
You must have the names of the following WebSphere® MQ objects:
Q Capture control tables
- A queue manager that the Q Capture program works with.
- A local queue to serve as the administration queue.
- A local queue to serve as the restart queue.
Q Apply control tables
- A queue manager that the Q Apply program works with.
Tip: Use the VALIDATE WEBSPHERE MQ ENVIRONMENT FOR command in the ASNCLP or the validate controls in the Replication Center to ensure that the queue managers and queues that you specify for the control tables exist and have the correct properties.

Restrictions

For partitioned databases, all of the table spaces that are used by the control tables must be in a single-partition table space that is on the catalog partition.

About this task

Each instance of the Q Capture program or Q Apply program has its own set of control tables, identified by the Q Capture schema or Q Apply schema. For example, the control table that stores operational parameters for a Q Capture program with a schema of ASN1 would be named ASN1.IBMQREP_CAPPARMS.

By default, the control tables are placed in two table spaces on z/OS®, one for tables that require page-level locking and one for tables that require row-level locking. The control tables are created by default in one table space on Linux, UNIX, and Windows. You can customize where each control table is created, and you can specify existing table spaces or create new table spaces.

Federated targets: If you are replicating to a non-DB2 target, see Creating Q Apply control tables for federated Q Replication.

For peer-to-peer replication, the Q Capture program and Q Apply program run as a pair at each server. Both sets of control tables must have the same schema.

Procedure

To create Q Capture or Q Apply control tables, use one of the following methods:

Method Description

Method	Description
ASNCLP command-line program	Use the CREATE CONTROL TABLES FOR command. For example, the following commands set the environment and create control tables in the SAMPLE database with a Q Capture schema of ASN1: `ASNCLP SESSION SET TO Q REPLICATION; SET SERVER CAPTURE TO DB SAMPLE; SET QMANAGER "QM1" FOR CAPTURE SCHEMA; SET CAPTURE SCHEMA SOURCE ASN1; SET RUN SCRIPT LATER; CREATE CONTROL TABLES FOR CAPTURE SERVER USING RESTARTQ "ASN1.QM1.RESTARTQ" ADMINQ "ASN1.QM1.ADMINQ" MEMORY LIMIT 64 MONITOR INTERVAL 600000;` The CREATE command specifies a restart queue and administration queue, doubles the default amount of memory available to build transactions to 64 MB, and reduces the default interval for recording performance information to 600000 milliseconds (one minute).
Replication Center	Use the Create Control Tables wizard. To open the wizards, right-click the Q Capture Servers folder and click Create Q Capture control tables, or right-click the Q Apply Servers folder and click Create Q Apply control tables.

ASNCLP command-line program

Use the CREATE CONTROL TABLES FOR command. For example, the following commands set the environment and create control tables in the SAMPLE database with a Q Capture schema of ASN1:

ASNCLP SESSION SET TO Q REPLICATION;
SET SERVER CAPTURE TO DB SAMPLE;
SET QMANAGER "QM1" FOR CAPTURE SCHEMA;
SET CAPTURE SCHEMA SOURCE ASN1;
SET RUN SCRIPT LATER;

CREATE CONTROL TABLES FOR CAPTURE SERVER
USING RESTARTQ "ASN1.QM1.RESTARTQ"
ADMINQ "ASN1.QM1.ADMINQ" MEMORY LIMIT 64
MONITOR INTERVAL 600000;

The CREATE command specifies a restart queue and administration queue, doubles the default amount of memory available to build transactions to 64 MB, and reduces the default interval for recording performance information to 600000 milliseconds (one minute).

Replication Center Use the Create Control Tables wizard. To open the wizards, right-click the Q Capture Servers folder and click Create Q Capture control tables, or right-click the Q Apply Servers folder and click Create Q Apply control tables.

Send your feedback | Information roadmap | The Q+SQL Replication Forum

Last updated: 2013-10-25