Syntax

DB2 PLAN=
plan_name {RN=
reg_ssid|CN=
conn_ssid|RN=
reg_ssid CN=
conn_ssid}
START {COLD|WARM|STARTLOC=
rba [USEDIR],[USESTAT]}
[CHKSCHEM {
NO|YES|WARN}]
[COMMITINT [MS=
milliseconds]]
[DB2ROWPROMOTION {
ENABLE|DISABLE}]
[EC PERMIL={
number_of_errors|
0}]
[IFI306 [OPT={N|Y|
F}] [4KPAGES={
nnn|
50} [NDWAIT={
nnnn|
300}]
[ROWNOTDECOMPRESSED {
FAIL|NOFAIL}]
[SHOWGENERATED]
[SKIPURDML 
eccr_description_of_urid]
[STAT LEV={
ST|SQ} [SEC=
seconds]]
[TRACE 
trace_id[,
trace_level]]

All of the statements must begin in column 1.
Keyword parameters in the statements are positional.

***********************************************************************
* Use only one START statement for an execution of the DB2 ECCR.      *
* Use only one DB2   statement for an execution of the DB2 ECCR.      *
* Other statements contain default values.                            *
*                                                                     *
* All the parameters below are column specific, beginning in column 1 *
***********************************************************************
START WARM
* START COLD
* START STARTLOC=00000000000000000000 USEDIR,USESTAT
* DB2 PLAN=DTLCPV80 RN=DSN1
DB2 PLAN=<
plan_name> RN=<
ssid> 
* DB2 PLAN=DTLCPV52         CN=DSN1
EC PERMIL=000
STAT LEV=ST SEC=3600
CHKSCHEM NO

Statement Descriptions

DB2 PLAN=

plan_name

{RN=

rn_ssid

|CN

=cn_ssid

|RN=

rn_ssid

CN=

cn_ssid

}

Specifies the DB2 plan and subsystem name or group name for the DB2 for z/OS system to which the DB2 ECCR attaches.

You can specify RN, CN, or both RN and CN. At least one of these keywords is required. If you specify RN or CN only, the specified keyword is used for the non-specified keyword.

When implementing the DB2 ECCR in a data-sharing environment, Informatica recommends entering the group attachment name for the RN keyword and for the registration group in the PowerExchange Navigator. The PowerExchange Logger uses the registration tag name to capture changes. The registration tag name contains the value specified in the

Database Instance

field in the registration group. By using the group attachment name, you make the registration tag names and captured change data independent of a specific data-sharing group member SSID.

PLAN=

plan_name

Identifies the DB2 plan name that the DB2 ECCR uses.

Ensure that your entry complies with the following rules:

The PLAN keyword must be in uppercase and begin in column 5.
Plan names must be in uppercase.
Plan names can be between 1 and 8 characters long.
Plan names less than eight characters must be padded with spaces to make eight characters.
For example, if your plan name is MYPLAN, you must add three spaces between the plan name and the RN keyword.

RN=

reg_ssid

Specifies the DB2 subsystem identifier that appears in the capture registrations.

This value must match the value that is specified in the

Database Instance

field in the registration group in the PowerExchange Navigator. If not specified, the CN value is used by default.

The following values are valid:

A DB2 subsystem ID (SSID) or DB2 group attachment name
An uppercase value of one to four characters in length that begins in column 19

CN=

connect_ssid

Specifies the DB2 subsystem identifier to which the DB2 ECCR connects. If not specified, the RN value is used by default.

The following values are valid:

A DB2 subsystem ID (SSID) or DB2 group attachment name
An uppercase value of one to four characters in length that begins in column 27

The following examples show combinations of RN and CN keywords:

If you have DB2 subsystem SS01 in non-data-sharing environment, use the following DB2 statement:
DB2 PLAN=
plan_name RN=SS01 
If you migrate subsystem SS01 to a data-sharing environment called GRP1, use the following DB2 statement:
DB2 PLAN=
plan_name RN=SS01 CN=GRP1 
If you add a DB2 subsystem, SS02, to the data-sharing group GRP, continue to use the previous statement to run one instance of the ECCR on either SS01 or SS02. You must continue to register new tables under the name SS01.
If you have a data sharing environment with the previous configuration and do not have existing capture registrations, use the following DB2 statement:
DB2 PLAN=
plan_name RN=GRP1 
Also, create all capture registrations under the GRP1 name.

Restart the DB2 ECCR to activate a change for this statement.

START {COLD|WARM|STARTLOC=

rba

[USEDIR],[USESTAT]}

Required. Controls the method by which the DB2 ECCR is started.

Options are:

COLD

Starts the ECCR for the first time or restarts the ECCR after a major system failure.

WARM

Restarts change-capture processing from the point where it last stopped, without loss of data.

Use this option to restart the ECCR after a successful shutdown with the STOP command or MODIFY QUIESCE command. Typically, you should use the WARM keyword when starting the ECCR.

STARTLOC=

rba

[USEDIR],[USESTAT]

Restarts change-capture processing from a specific point in the DB2 log.

The

rba

value specifies the 20-digit hexadecimal RBA value or the log record sequence number (LRSN) at which the DB2 ECCR should start in the DB2 log.

The following keywords are optional:

USEDIR
. The ECCR uses the source table information from the data-resource information that was registered in the PowerExchange when the STARTLOC option was specified.
USESTAT
. The ECCR uses a status of active (C) or inactive (N) for the table registration that existed when the STARTLOC option was specified.

If you change this statement, you must restart the ECCR to activate the new setting. The new setting is ignored if you REFRESH the ECCR.

CHKSCHEM {

NO

|YES|WARN}

Optional. Specifies whether the DB2 ECCR verifies schema registrations at ECCR startup. Also determines how errors, if found, are handled. This schema verification processing is in addition to the verification processing that is performed when the ECCR receives the first change record for a registered schema.

Options are:

NO
. Does not verify registered schema at ECCR startup. When the ECCR receives the first change record for a schema, the ECCR verifies each registered schema against the information in the DB2 catalog.
YES
. Verifies all registered schema information against the information in the DB2 catalog at ECCR startup and when you refresh the ECCR. If the verification process encounters errors, the ECCR ends.
WARN
. Verifies all registered schema information against the information in the DB2 catalog at ECCR startup and when you refresh the ECCR. If the verification process encounters errors, the ECCR issues a warning message and continues processing.

Default is NO.

Refresh or restart the DB2 ECCR to activate a change for this statement.

COMMITINT [MS={

milliseconds

|

60000

}]

Optional. Specifies the time interval, in milliseconds, after which the DB2 ECCR issues an SQL COMMIT to free resources that are held on its behalf because of IFI306 activity.

Valid values are 0 through 999999. Default is 60000 milliseconds, or 60 seconds.

A value of 0 disables time-based SQL COMMITs. The ECCR issues SQL COMMITs only after the following types of events:

ECCR startup
Processing of the DB2 ECCR REFRESH command
Processing of a UR that contains DDL

DB2ROWPROMOTION {

ENABLE

|DISABLE}

Controls how the DB2 ECCR handles old images in DML rows. Options are:

ENABLE
. The ECCR uses the DB2 READS API to convert CDC row data to the version that is current at the time of the DML operation.
DISABLE
. The ECCR processes old images in rows for DML changes as usual.

Default is ENABLE.

Do not change the default value unless Informatica Global Customer Support directs you to do so.

EC PERMIL={

number_errors

|

0

}

Optional. Specifies the maximum number of acceptable errors per thousand updates.

Default value is 0.

Refresh or restart the DB2 ECCR to activate a new value for this statement.

IFI306 [OPT={N|Y|

F

}] [4KPAGES={

nnn

|

50

}] [NDWAIT={

nnnn

|

300

}]

Optional. Controls the DB2 ECCR interaction with the DB2 instrumentation facility interface (IFI). This statement requires at least one of the following keyword parameters: OPT, 4KPAGES, or NDWAIT.

OPT

Specifies how the DB2 ECCR reads the DB2 log. Enter this keyword in all uppercase beginning in column 8.

Options are:

Y
. Returns CDC records from the DB2 log.
N
. Returns all records from the DB2 log.
F
. Returns CDC records from the DB2 log and filters them by registered tables.

Default is F.

Do not change the default value unless Informatica Global Customer Support directs you to do so.

4KPAGES

Specifies the number of 4-KB pages of KEY-7 CSA storage to use for the DB2 IFI 306 buffer that stores the data to pass to the ECCR.

Enter the keyword in all uppercase beginning in column 14. For the keyword value, you can enter up to three digits. If you enter a value less than three digits, pad the value with spaces ending in column 24.

Default is 50.

Do not change the default value unless Informatica Global Customer Support directs you to do so.

NDWAIT

Specifies the interval, in hundredths of a second, that the ECCR waits for DB2 to return change data before sending another request to IFI to retrieve change data from the DB2 logs.

Enter this parameter in all uppercase beginning in column 26.

Valid values are 1-9999. Default is 300.

If you add, remove, or change the IFI306 statement, you must restart the DB2 ECCR for the change to take effect.

ROWNOTDECOMPRESSED {

FAIL

|NOFAIL}

Optional. Indicates whether the DB2 ECCR continues or fails when it encounters row data that has not been decompressed for a table with an active capture registration. This situation can occur, for example, if a REORG operation causes the DB2 compression dictionary to become invalid.

Options are:

FAIL
. If the ECCR encounters rows with compressed data, it ends abnormally. PowerExchange issues error message PWXEDM177462E to the EDMMSG data set and as a WTO message.
NOFAIL
. If the ECCR encounters rows with compressed data, it skips them and continues reading the DB2 log. PowerExchange issues informational messages PWXEDM177462I and PWXEDM177596I to the EDMMSG data set and as WTO messages.

Default is FAIL.

You can use the WTO messages to automate alert notifications to the appropriate system users.

SHOWGENERATED

Include this optional statement if you want the ECCR to list internally generated control statements in its output. If you have many capture registrations, the SHOWGENERATED statement can substantially increase the amount of ECCR output that is written to the EDMMSG data set. By default, the internally generated control statements are suppressed because they are not needed for normal operation. However, if you need them for debugging purposes, include this SHOWGENERATED statement.

SKIPURDML

eccr_description_of_urid

Optional. Causes the DB2 ECCR to skip operations in a specific DB2 unit of recovery (UR) when capturing changes. Use this statement to have the ECCR skip change records from a problematic area of the log. The

urid

value is the ECCR description of the DB2 URID, which consists of 20 hexadecimal characters, a period, and four ending hexadecimal characters. For example:

SKIPURDML 000000000004AB60DEC0.0000

Use this statement only at the direction of Informatica Global Customer Support.

You can specify up to 255 SKIPURDML statements in the REPL2OPT DD data set.

If you specify this parameter, the ECCR issues messages PWXEDM177230I and PWXEDM177231W to describe the UR and each log record that is skipped.

STAT LEV={

ST

|SQ} [SEC={

seconds

|

3600

}]

Optional. Controls the detail level of the PWXEDM177085I statistics message that the DB2 ECCR writes for tables of CDC interest to the EDMMSG data set. Also, optionally specifies the interval at which the ECCR issues the PWXEDM177084I and PWXEDM177085I statistics messages. The ECCR writes the statistics messages to the EDMMSG data set at the following points in time:

At ECCR termination
When you issue the ECCR DISPLAY command
When you issue the ECCR REFRESH command
When the reporting interval that is specified by the SEC parameter in this statement elapses

The ECCR writes PWXEDM177085I capture statistics only for tables for which change records have been captured. You can use the DISPLAY command with the ALL parameter to print the statistics for all source tables, including those with no change capture activity. For more information, see the

PowerExchange Command Reference

.

LEV={

ST

|SQ}

Identifies the detail level of the PWXEDM177085I table statistics that PowerExchange writes to the EDMMSG data set. Options are:

ST
. Writes summary statistics. Summary statistics are the total number of changes that the DB2 ECCR captured since the ECCR started, including backout records.
SQ
. Writes detail-level statistics. Detail-level statistics are counts of the inserts, updates, and deletes that were captured for each table that had some DML change activity.

Default is ST.

SEC={

seconds

|

3600

}

Optional. Specifies the number of seconds in the statistics reporting period. Default is 3600 seconds, or 1 hour.

If you update this statement, you must refresh or restart the DB2 ECCR to activate the change.

TRACE

trace_ID

[,

trace_level

]

Enables a trace that provides diagnostic information for troubleshooting DB2 ECCR problems.

Use this statement only at the direction of Informatica Global Customer Support.

In this statement, the

trace_id

is a trace type identifier. The trace level is a number from 1 to 9. Customer Support will provide the trace ID and the optional trace level if needed.

To activate more than one trace, you must enter the TRACE statement multiple times.

If you change the TRACE statement, you must restart the DB2 ECCR.