Configuring Db2 for z/OS for Q Replication and Event Publishing

Q Replication and Event Publishing for z/OS® require you to set parameters, authorize user IDs to run statements in Db2® for z/OS, and bind packages into specific plans.

1. Set the DSNZPARM parameters in the DSN6SYSP macro to the following recommended values:

   CONDBAT=600
   CTHREAD=800
   IDBACK=200
   IDFORE=400
   MAXDBAT=600

   Increasing the value IDFORE parameter value from 40, the default value, to 400 prevents you from exceeding the maximum number of thread connections. If you exceed the maximum number of connections, you will receive error message 00F30055:

   The maximum number of concurrent identify level agents has been exceeded.
   This abend code is issued by the following CSECT: DSN3ID30

2. Set IBM® MQ parameters in the CSQ6SYSP macro.
   See Configuring IBM MQ for Q Replication and Event Publishing for details.
3. Authorize user IDs that operate the Q Capture, Q Apply, and Replication Alert Monitor programs to run all of the Db2 for z/OS statements that are listed in Db2 authorizations required by replication and publishing on z/OS.
4. Bind any necessary packages.
   Db2 packages and plans for replication and event publishing on z/OS describes which Db2 packages to bind into plans for replication and publishing programs. Follow these steps:
   1. Bind packages for local subsystems. Run the ASNQBNDL sample job to bind packages for the replication and publishing programs (Q Capture, Q Apply, and Replication Alert Monitor).
   2. Bind packages for remote subsystems. If the Q Apply program or the Replication Alert Monitor needs to access a remote subsystem, a remote database, or a remote federated database, you must bind the packages that the program requires both on the remote Db2 for z/OS database and on the local Db2 for z/OS database. The plan must include the local and remote packages. Run the ASNQBNDR sample job to bind packages for the Q Apply program or the Replication Alert Monitor.