IBM Books

Replication Guide and Reference


Operating Capture for VM

The replication administrator can use the commands in this section to operate Capture for VM.

This section explains how to perform the following Capture for VM tasks:

Before You Start the Capture program

Before starting the Capture program, make sure you complete the following post-installation tasks:

A Capture program ASNPARMS file is provided that contains default values that the Capture program uses. Changing this file modifies the defaults. If you need different values for a specific database, copy the file to the Capture program virtual machine's A-disk. The following default values are contained in the Capture program ASNPARMS:

By default, the messages are issued in American English (ASNLS001). To issue messages in a different language, change the LANGUAGE parameter in the ASNPARMS file. Supported languages include:

Starting Capture for VM

After it starts, the Capture program runs continuously until you stop it or it detects an error.

To start the Capture program:

 Starting the Capture program
 
>>-ASNCCP---+--------+-+---------+-+--------+-+---------+------->
            +-WARM---+ +-PRUNE---+ +-TERM---+ +-TRACE---+
            +-COLD---+ +-NOPRUNE-+ +-NOTERM-+ +-NOTRACE-+
            +-WARMNS-+
 
>--+------------------------------+----------------------------><
   +-NOUSERID---------------------+
   +-USERID=--auth_name/password--+
 

If conflicting invocation parameters are specified, Capture for VM uses the value of the last parameter specified. For example, if ASNCCP is started using the COLD TRACE NOTRACE parameter string, no informational event trace will be written (NOTRACE).

Table 18 defines the optional parameters.

Table 18. ASNCCP Command Parameter Definitions for VM

Parameter
Definition

Src_server
Source server name positional parameter that must be the first parameter if entered. If not specified, the value from the DB2DBDFT environment variable will be used.

WARM  (default) 
The Capture program resumes processing where it ended in its previous run if warm start information is available. If the Capture program cannot warm start, it switches to a cold start. See "Warm and Cold Starts" for more information.

WARMNS
The Capture program resumes processing where it ended in its previous run if warm start information is available. Otherwise, it issues a message and terminates. With WARMNS, the Capture program does not automatically switch to a cold start. The Capture program leaves the trace, UOW, change data, and warm start tables intact. In case of errors, the Capture program terminates instead of switching to a cold start as when WARM is specified. See "Warm and Cold Starts" for more information.

COLD
The Capture program starts by deleting all rows in its change data, UOW, pruning control, and trace tables during initialization. See "Warm and Cold Starts" for more information.

PRUNE  (default) 
The Capture program automatically prunes the change data and UOW tables.

NOPRUNE
Automatic pruning is disabled. The Capture program prunes the change data and UOW tables when you enter the PRUNE command. See the PRUNE command for more information.

NOTRACE  (default) 
No trace information is written.

TRACE
Writes debug trace messages to the standard output, stdout.

USERID=auth_name/password
Specifies that the Capture program should connect to the database as user ID auth_name. The correct password must be provided or an error is returned. The auth_name and password are both from 1 to 8 characters in length.

For VM/ESA, if you do not specify this parameter, the Capture programconnects to the database as the user ID on which you issue ASNCCP.


Stopping the Capture program for VM

STOPPING CAPTURE
 
>>-STOP--------------------------------------------------------><
 

Purpose

Use the STOP command to stop the Capture program gracefully and commit the log records that it processed up to that point.

STOP should be issued before:

Usage

If you stop the Capture program, it shuts itself down and issues an informational message. If it detects an error, the program shuts itself down after cleaning up the data in the affected tables (so that the data will not be used). Staging tables are pruned when it is appropriate. In the case of re-IPL or logoff, you must initiate a cold start because the warm start information could not be saved.

Capture for VM issues informational or error messages to the console.

Suspending Capture for VM

Suspending the Capture program
 
>>-SUSPEND-----------------------------------------------------><
 

Purpose

Use the SUSPEND command to suspend the Capture program until you issue the RESUME command.

Usage

You can use this command to suspend the Capture program to improve performance for operational transactions during peak periods without destroying the Capture for VM program run environment.

Resuming Capture for VM

Resuming the Capture program
 
>>-RESUME------------------------------------------------------><
 

Purpose

Use the RESUME command to resume the suspended Capture program.

Usage

You can use this command to resume the Capture program if you suspended it with the SUSPEND command.

Reinitializing Capture for VM

Reinitializing the Capture program
 
>>-REINIT------------------------------------------------------><
 

Purpose

Use the REINIT command to reinitialize the Capture program.

Usage

Use the REINIT command to begin to capture changes from new source tables if you add a new replication source with the Control Center while the Capture program is running. This command ensures that the Capture program recognizes the new replication sources in the change data control table. To allow the new replication source to be visible to the Capture program, you must issue a REINIT command. The REINIT command tells the Capture program to obtain newly added replication sources from the change data control table (ASN.IBMSNAP_REGISTER).

REINIT also rereads the tuning parameters table (ASN.IBMSNAP_CCPARMS) for any changes made to the tuning parameters.

Attention: Do not use REINIT to reinitialize the Capture program after canceling a replication source or dropping a replication source table while the Capture program is running. Instead, stop the Capture program and use warm start.

Pruning the Change Data and Unit-of-Work Tables

Pruning the Capture program
 
>>-PRUNE-------------------------------------------------------><
 

Purpose

Use the PRUNE command to initiate the pruning of the change data (CD) and unit-of-work (UOW) tables, if you used the NOPRUNE invocation parameter on ASNCCP.

Usage

This command prunes tables once. During pruning, if you stop or suspend the Capture program, pruning does not resume after you enter the RESUME command. You must enter the PRUNE command again to resume pruning.

Providing the Current Log Sequence Number

Getting the Log
 
>>-GETLSEQ-----------------------------------------------------><
 

Purpose

Use the GETLSEQ command to provide the timestamp and current log sequence number.

Usage

Use the GETLSEQ command to determine how far the Capture program has read the log.


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

[ DB2 List of Books | Search the DB2 Books ]