AI
. Stores only after images in the PowerExchange Logger log files.
BA
. Stores both before and after images in the PowerExchange Logger log files.

You cannot use before images of the data in extraction processing. If you add before image (BI) fields to extraction maps, PowerCenter CDC sessions that reference the BI fields fail.
If you add change indicator (CI) fields to extraction maps, PowerCenter CDC sessions that reference the CI fields fail.

Uppercase and lowercase letters
The numbers 0 to 9
Spaces
The following special characters:
’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ? 
The first character is an apostrophe.

CAPTURE_NODE_PWD="This is a passphrase!"

If the SECURITY setting is 0, do not specify this parameter. PowerExchange uses the user ID under which the PowerExchange Listener job runs to control access to capture registrations and change data.
If the SECURITY setting is 1, enter a valid operating system user ID for this parameter. Otherwise, error message PWX-00231 is issued, indicating a signon failure. However, PowerExchange uses the user ID under which the PowerExchange Listener job runs to control access to capture registrations and change data.
If the SECURITY setting is 2, enter a valid operating system user ID for this parameter. Otherwise, error message PWX-00231 is issued, indicating a signon failure. PowerExchange uses this user ID to control access to capture registrations and change data. If the specified user ID does not have the authority that is required to read capture registrations or change data, access fails.

For Db2 sources on Linux, UNIX, or Windows, enter a valid operating system user ID that has Db2 DBADM or SYSADM authority.
For Microsoft SQL Server instances that use SQL Server Authentication, enter a database user ID that permits access to the SQL Server distribution database. For SQL Server instances that use Windows Authentication, PowerExchange uses the user ID under which the PowerExchange Listener was started. In this case, do not specify this parameter unless you want to specify another user.
For MySQL sources on Linux or Windows, enter a database user ID that allows access to the MySQL binary logs. This user must have been granted the privileges that are required for MySQL CDC. For more information, see Preparing MySQL Sources.
For Oracle sources, enter the ORACAPTL user ID that you defined, which permits access to the Oracle online and archive redo logs.
For PostgreSQL sources on Windows, enter a database user ID that allows access to the PostgreSQL source database. This user must have been granted the privileges that are required for PostgreSQL CDC. For more information, see Preparing PostgreSQL CDC Sources.

0
. Runs the PowerExchange Logger continuously until you manually stop it. After the Writer subtask completes a processing cycle, it waits for the number of minutes specified in the NO_DATA_WAIT parameter before starting another processing cycle.
1
. Runs the PowerExchange Logger in batch mode. The PowerExchange Logger shuts down after the seconds specified in the NO_DATA_WAIT2 parameter elapse and no data has been received.

If you set the retention period to a low value, ensure that PowerExchange extracts change data from the PowerExchange Logger log files during this period. Otherwise, the log files for which the retention period has elapsed are deleted and you can lose change data. For example, if the retention period is 5 and you plan not to run extractions during a 10-day holiday, increase the retention period to 15. This approach ensures that the log files with the change data you need are not deleted until the extractions run again.
If you set the retention period to a high value, the CDCT can become very large, depending on the number active capture registrations. Also, the number of PowerExchange Logger log files might increase. For continuous extraction mode, you can use the PowerExchange Logger FILE_SWITCH parameters to decrease the number of log files and increase their size instead.
If you use continuous extraction mode, PowerExchange reads the CDCT file each time the interval specified in the FILEWAIT parameter of the CAPX CAPI_CONNECTION statement elapses. If a CDCT file becomes large, this read activity can increase I/O, system resource use, and latency of change data extraction. If you use batch extraction mode, this high read activity is not a consideration.

For Db2 sources on Linux, UNIX, or Windows, enter the
Database
name that is displayed for the registration group in the
Resource Inspector
.
For Microsoft SQL Server, this value depends on whether you also specify the optional DISTSRV and DISTDB parameters in the PowerExchange Logger configuration file and whether you entered the
Instance
identifier when creating the registration group:
If you specify the optional DISTSRV and DISTDB parameters to have the single PowerExchange Logger instance log data for all of the registered articles that are published to the distribution database, enter a name that serves as the collection identifier for all of the registrations. This name must be one to eight characters in length and start with a letter. This name overrides the instance name that is associated with the individual registrations.
When you perform a CAPXRT database row test, you must enter this name in the
MSS LUW DBId
field in the CAPXRT Advanced Parameters dialog box. When you define a PWXPC connection for PowerCenter CDC sessions that extract data from PowerExchange Logger log files, enter this value for the
Logger DBID
attribute on the PowerCenter PWX MSSQL CDC Real Time connection.
If you do not specify the DISTSRV and DISTDB parameters, enter the value from the
Instance
field that is displayed for the registration group in the PowerExchange Navigator Resource Inspector. The instance identifier is either the unique user-defined identifier that was optionally entered for the database name and database server combination during registration group creation in the PowerExchange Navigator or the instance identifier that PowerExchange generated if you did not specify an instance identifier.
For MySQL, enter the
Instance
name that is displayed for the registration group in the
Resource Inspector
.
For Oracle, enter the
Instance
name that is displayed for the registration group in the
Resource Inspector
. This value also should match the first positional parameter of the ORACLEID statement in the dbmover configuration file.
For PostgreSQL, enter the
Instance
name that is displayed for the registration group in the
Resource Inspector
.

For Adabas, enter the
Instance
name that is displayed for the registration group.
For Datacom, enter the
MUF Name
value that is displayed for the registration group.
Alternatively, if you use Datacom synchronous CDC, enter the value of the MUF parameter in the DTLINPUT data set specified in the MUF JCL. Or, if you use Datacom table-based CDC, enter the value of REG_MUF parameter in the ECCRDCMP member of the RUNLIB library.
For Db2 for i, enter the
Instance
name that is displayed for the registration group. This name should match the INST parameter value in the AS4J CAPI_CONNECTION statement in the DBMOVER member of the CFG file.
For Db2 for z/OS, enter the
Instance
name that is displayed for the registration group. This name should match the RN parameter value in the DB2 statement in the RUNLIB(REPDB2OP) member.
For IDMS Log-based CDC, enter the
Logsid
value that is displayed for the registration group. This value should match the LOGSID parameter value in the RUNLIB(ECCRIDLP) member.
For IMS, enter the
IMSID
value that is displayed for the registration group. For IMS log-based CDC, this value should match the first parameter value in the IMSID statement in the RUNLIB(CAPTIMS) member.
For VSAM, enter the
Instance
name that is displayed for the registration group.

MSS
for Microsoft SQL Server sources
MYS
for MySQL sources
ORA
for Oracle sources
PGS
for PostgreSQL sources
UDB
for Db2 sources on Linux, UNIX, or Windows

ADA
for Adabas sources
AS4
for Db2 for i sources
DB2
for Db2 for z/OS sources
DCM
for Datacom sources.
IDL
for IDMS log-based CDC sources
IMS
for IMS sources
VSM
for VSAM sources

/capture/pwxlog

EXT_CAPT_MASK=\\\host\Shared Folders\C\CDC_SHARED\logfiles

.CND.CP
yymmdd.T
hhmmssnnn

yymmdd
is a date composed of a two-digit year, a month, and a day.
hhmmss
is 24-hour time value, including hours, minutes, seconds.
nnn
is a generated sequence number that ensures uniqueness of the file name.

/capture/pwxlog.CND.CP080718.T1545001

-1
. The PowerExchange Logger does
not
flush outstanding change data to the current log file on disk based on this parameter. Enter this value only if you use batch extraction mode. If you use continuous extraction mode, this value can increase the latency of your continuous extraction sessions.
0
. The PowerExchange Logger flushes outstanding change data after every record.
Any value from 1 through 86400
. The PowerExchange Logger flushes outstanding change data at the specified interval.

M
for minutes.
R
for records.

Y
. Enables automatic file switches when checkpoint events occur.
N
. Disables automatic file switches when checkpoint events occur.

IBMIJRNLOVRD=(JRN=MYSCHEMA/QSQJRN,FROMRCVR=MYSCHEMA/QSQJRN1047,TORCVR=MYSCHEMA/QSQJRN1047)

Y
. The PowerExchange Logger deletes expired CDCT records during file switches. You cannot use the PWXUCDCT utility DELETE_EXPIRED_FILES command to manually delete expired log files and their related CDCT records.
N
. The PowerExchange Logger does not delete expired CDCT records. However, you can use the PWXUCDCT utility DELETE_EXPIRED_FILES command to manually delete expired log files and their related CDCT records.
This parameter does not affect PowerExchange Logger deletions of CDCT records that are rolled back because of a cold start or a warm start to a prior point in time.

Cold start the PowerExchange Logger.
Warm start the PowerExchange Logger from a previous position in the change stream. This situation occurs only if the CDCT file still contains records related to the deleted files.

Y
. Displays the confirmation message PWX-33236 for a cold start or PWX-33242 for a warm start. You must respond to the message for startup processing to continue.
N
. Does not display the confirmation messages. PowerExchange attempts to start without first prompting for user confirmation.

If you do not specify these parameters, processing starts from the current end-of-log position.
If you enter 0 for both parameters, processing starts from the default start location for the source type, as follows:
For Db2, the default location is the current log position at the time the PowerExchange capture catalog was created.
For Microsoft SQL Server, the default location is the oldest data available in the publication database.
For MySQL, the default location is the oldest data available in the binary log. This position is the beginning of the binary log that has the log name that includes the lowest numeric suffix value. You can use the SHOW BINARY LOGS statement to identify this log.
For Oracle, the default location is the beginning of the most recent archive log.
For PostgreSQL, the default location is the oldest data stored in the replication store table. If the replication store table is empty, the default location is the oldest record waiting to be read from the logical replication slot.
If you enter restart token and sequence token values other than 0, processing resumes from the specific restart point defined by these token values. To perform a special start of the PowerExchange Logger, you must specify the RESTART_TOKEN and SEQUENCE_TOKEN parameters with specific values, and the SEQUENCE_TOKEN value must be greater than the sequence token in the CDCT file.

N
. The PowerExchange Logger does not automatically trap and handle system errors. Instead, the operating system uses default error handling. Usually, the default handing is to report the program line in error and dump memory.
Y
. The PowerExchange Logger automatically handles certain errors such as memory corruption. After the PowerExchange Logger handles the error, it attempts to shut down in a controlled manner.

PowerExchange Logger process ID (PID)
Status of the PowerExchange Logger Writer task
CPU time used by the PowerExchange Logger - total and for Writer task functions.
Memory use (current/total/maximum) in kilobtyes, total and for the Controller, Command Handler, and Writer tasks
Record counts, including the number of inserts, updates, deletes, and commits that the PowerExchange Logger processed - total since the Logger started and for the current active log file and the active logging cycle
Total number of UOWs and bytes that the Writer task processed

The number of DML operations and commits processed for each group
Then number of change records that have not yet been flushed to a Logger log file on disk
The name of the open Logger log file for each group and the file open timestamp

You enter the DL or DG command at the command line, or enter the pwxcmd displaystats -tp {logger|groups} command from a remote Linux, UNIX, or Windows system.
You issue the SHUTCOND or SHUTDOWN command to a PowerExchange Logger that runs in continuous mode.
A PowerExchange Logger that runs in batch mode finishes its run and shuts down.

{

interval

|

0

}

Optional. The interval, in minutes, after which PowerExchange publishes monitoring statistics for the PowerExchange Logger. The interval-based statistics that are written to the PowerExchange message log file are the same as those published by the DL (or DS) command and

pwxcmd displaystats -tp logger

command. However, a subset of the message output is displayed on screen to prevent flooding the screen with messages over time.

The Logger still issues monitoring messages at shutdown, regardless of whether you specify the

interval

parameter.

Valid values are 0 through 120. Default is 0, which disables interval-based reporting of PowerExchange Logger monitoring statistics. With the default value, PowerExchange writes these statistics only when one of the following Logger commands is issued: DL,

pwxcmd displaystats -tp logger

, SHUTCOND, or SHUTDOWN.

Y
. Verbose messaging. The PowerExchange Logger logs multiple messages at various processing points, such as when starting or ending a cycle of reading source data or doing a file switch. Verbose messaging often includes processing statistics such as records processed and elapsed time.
N
. Terse messaging. The PowerExchange Logger logs a single terse message for each file switch.