Replication Guide and Reference

Configuring the Capture and Apply Programs

The following sections provide instructions for configuring the Capture and Apply programs for Windows NT, and for providing end-user authentication at the source server.

Configuring the Capture Program

To configure the Capture program:

From the source server system, ensure that the user ID under which the Capture program is to run has the required privileges:
- Execute privilege on the Capture packages
- DBADM or SYSADM privileges for the database
Log on with the user ID.
From the DB2 command line processor or the Command Center, connect to the source server database by entering:
```
DB2 CONNECT TO SAMPLE
```
Change to the \SQLLIB\BND directory, which is where the bind files are located.
Create and bind the Capture program package to the source server database by entering the following command:
```
DB2 BIND @CAPTURE.LST ISOLATION UR BLOCKING ALL
```
If your system does not support uncommitted read format, substitute CS (cursor stability format) for UR instead.
These commands create a list of packages, the names of which can be found in the CAPTURE.LST file.

Configuring the Apply Program

To configure the Apply program:

From the source, control, and target server system, ensure that the user ID under which the Apply program is to run has the required privileges:
- Execute privilege on ASNAPPLY
- DBADM or SYSADM privileges for the database
Log on with the user ID.
Connect to the source server database by entering:
```
DB2 CONNECT TO SAMPLE
```
Create and bind the Apply package to the source server database by entering both of the following commands:
```
DB2 BIND @APPLYUR.LST ISOLATION UR BLOCKING ALL
```
```
DB2 BIND @APPLYCS.LST ISOLATION CS BLOCKING ALL
```
These commands create a list of packages, the names of which can be found in the APPLYUR.LST and APPLYCS.LST files.
Connect to the target server database by entering:
```
DB2 CONNECT TO COPYDB
```
Create and bind the Apply package to the target server database by entering both of the following commands:
```
DB2 BIND @APPLYUR.LST ISOLATION UR BLOCKING ALL
```
```
DB2 BIND @APPLYCS.LST ISOLATION CS BLOCKING ALL
```
These commands create a list of packages, the names of which can be found in the APPLYUR.LST and APPLYCS.LST files.

Providing End-User Authentication at the Source Server

For end-user authentication to occur at the source server, you must provide a password file with an AUTH=SERVER scheme for the Apply program to use when connecting to the source server. It is advisable to limit read access of this file to the user ID that will run the Apply program.

The password file must meet the following criteria:

Have a file name as shown:
```
<APPLYQUAL><instname><CNTLSRVR>.PWD
```
Where:

APPLYQUAL
The Apply qualifier in uppercase.
instname
The instance name that the Apply program runs under (value of DB2INSTANCE).
CNTLSRVR
The name of the control server in uppercase.
Reside in the directory from which the Apply program starts.
Contain all server-name/password pairs. The pairs enable you to have a different (or the same) password at each control server. The Apply user ID is used for all connections.

To create a password file:

Type the following records in your editor. Do not include blank lines or comment lines in the file.
```
SERVER=SAMPLE PWD=password
```
```
SERVER=COPYDB PWD=password
```
Save the file as DEPTQUALdb2COPYDB.PWD.

For more information about authentication and security, refer to the IBM DB2 Administration Guide for common servers.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]