The IBM Replication administrator user ID can use the commands in this section to operate Capture for Windows NT and Windows 95. Enter the commands or key combinations from an NT window.
This section explains how to perform the following Capture program tasks:
Before starting the Capture program, make sure you complete the following post-installation tasks:
You can also create these control tables manually by running the DPCNTL.* file from the RUN SQL Files window.
After you start the Capture program, it runs continuously until you stop it or it detects an error.
To start the Capture program using the NT services:
You can also start the replication service by typing STRTSERV on the NT command line.
To start the Capture program using the DB2 command window:
SET DB2INSTANCE=database_instance_name
While the Capture program is running, a file with the name <database_instance_name><database_name>.CCP is created in the directory from which the Capture program is invoked. This file is a log file for the messages issued by the Capture program; these messages are also recorded in the ASN.IBMSNAP_TRACE table.
>>-ASNCCP--+------------+---+--------+---+---------+---+---------+->
'-Src_server-' +-WARM---+ +-PRUNE---+ +-NOTRACE-+
+-WARMNS-+ '-NOPRUNE-' '-TRACE---'
'-COLD---'
>--------------------------------------------------------------><
Table 11 defines the optional parameters.
Table 11. ASNCCP Command Parameter Definitions for Windows NT or Windows 95
|
|---|
|
|
|
|
Use the AT command to start the Capture program at a specific time. For example, the following command string starts the Capture program for Windows NT at 15:00.
c:\>AT 15:00 /interactive "c:\SQLLIB\BIN\db2cmd.exe c:\CAPTURE\asnccp.exe cold"
| Note: | The Windows NT or Windows 95 Schedule Service must be started before using the AT command. |
If you started the Capture program as an NT service, stop ASNCCP by selecting Replication from the NT Services window and clicking the STOP push button. After the stop message appears, the status field becomes blank.
If you started the Capture program from the DB2 command window, enter the following command:
>>-ASNCMD--STOP------------------------------------------------><
or one of the following:
Use the STOP command or the key combination to stop the Capture program in an orderly way and commit the log records that it processed up to that point.
Stop the Capture program before:
In some situations, you might want to trigger the stop of the Capture program. For example, you might want to stop it at a specific time, or after all transactions for a particular application have been committed. The simplest way to set up this trigger is to create a table (or use an existing table), define it as a replication source, and identify a particular column whose update, when captured, triggers shutdown.
To stop the Capture program with a trigger:
Use the following example as a guideline.
When your application encounters STOPCAP in the change data table, it should issue the command to stop the Capture program.
>>-ASNCMD--SUSPEND---------------------------------------------><
Use the SUSPEND command to relinquish Windows NT or Windows 95 resources to operational transactions during peak periods without destroying the Capture program environment.
This command suspends the Capture program until you issue the RESUME command.
To use the command, do the following from a different window than where the Capture program is running:
Attention: Do not use SUSPEND when canceling a replication source. Instead, stop the Capture program using Ctrl+C.
>>-ASNCMD--RESUME----------------------------------------------><
Use the RESUME command to resume the suspended Capture program.
To use the command, do the following from a different window than where the Capture program is running:
>>-ASNCMD--REINIT----------------------------------------------><
Use the REINIT command to make the Capture program reread the ASN.IBMSNAP_REGISTER tables or the ASN.IBMSNAP_CCPPARMS table while it is running. Use this command when 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 source. The Capture program also rereads the ASN.IBMSNAP_CCPPARMS table 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 (WARM or WARMNS).
To use the command, do the following from a different window than where the Capture program is running:
>>-ASNCMD--PRUNE-----------------------------------------------><
Use the PRUNE command to start pruning the change data (CD) table and the unit-of-work (UOW) tables if you used the NOPRUNE invocation parameter to disable pruning when you started the Capture program. This command prunes the CD and UOW tables once. The Capture program issues the message ASN0124I when the command is successfully queued.
To use the command, do the following from a different window than where the Capture program is running:
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.
>>-ASNCMD--GETLSEQ---------------------------------------------><
Use the GETLSEQ command to provide the timestamp and current log sequence number. You can use this number to determine how far the Capture program has read the DB2 log.
To use the command, do the following from a different window than where the Capture program is running: