Navigator User Guide

10.5.3
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.2
- 10.5.1
- 10.5
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

CAPXRT Advanced Parameters Dialog Box - General Tab

On the

General

tab of the

CAPXRT Advanced Parameters

dialog box, define any optional override parameters that you want to use for the database row test of real-time access to change data.

Extract Type: The extraction type. Select one of the following options:

RS
. Restarts the extraction from the start point of the last extraction. This option enables you to run the same extraction multiple times.

SL
. Starts the extraction from the point at which the last extraction ended. The extraction uses restart tokens for z/OS or checkpoint timestamps for i5/OS.

CC
. Starts the extraction from the point that is indicated by the token values the
Restart Token 1
and
Restart Token 2
fields on this tab. If you select this option, you must specify valid token values.
For z/OS sources, if you use the default value of Y for the FUZZYRSTART parameter in the LRAP CAPI_CONNECTION statement, you can enter a
Restart Token 2
position other than a begin-uow position from which to start extraction processing in the PowerExchange Logger for z/OS logs. In the following example, the
Restart Token 2
value points to a RBA position that does not coincide with a begin-uow record and the
Restart Token 1
value points to a position before the
Restart Token 2
position:

In the
Restart 1
field, specify
000000000001000000000000000000000000000000000000
. This value consists of 48 zeroes with a "1" in the twelfth position. With this value, the Restart Token 2 value will determine the records to be returned by the row test.
In the
Restart 2
field, specify a value that consists of a 6-byte Logger ID in EBCDIC format (padded with spaces) + a 6-byte RBA position + 8 zeroes. The RBA position can be any RBA in the logs near where you want to restart extraction processing. For example:
E2C2F2D340400000000AEF4000000000

With these restart token settings, PowerExchange begins extraction processing at the first record that is at or past the Restart 1 position and in the first UOW that is returned based on the Restart 2 position.

Default is
RS
.
Image Type: The capture image type. Select one of the following options:

AI
. Captures the after-image data.

BA
. Captures the before-image data as it existed before the latest change. Also, captures the after-image data as it existed after the latest change.

The before-image data is shipped with an action character forcing the deletion of the record. The after-image data, which includes the change data, is delivered as an insert operation.

TU
. Captures the before- and after-image data, as it occurs. The application uses the before-image data to verify that no changes occurred in the record since the request. The after-image data appears as an update operation. The update is a full image, but the application that captures this update can change the target record instead of deleting the record and then inserting a new record, as occurs with BA. The TU option with ODBC connections.

Default is
AI
.
Timeout: The maximum amount of time, in seconds, to wait for data before returning an end-of-file (EOF).

Valid values are:

0. Returns the EOF when the end of the current log is reached. The end of the log is determined at the start of the extraction process, because the actual end point constantly changes.

2 to 86399. Waits the specified number of seconds for data before returning the EOF.

86400. Waits continually for an unlimited amount of time, without returning the EOF.

Default is 15.
No Progress Update: Indicates whether to add database row test output to the PowerExchange CDC audit trail for the application.

Select this check box to omit database row test output from the PowerExchange CDC audit trail.

Clear this check box to include database row test output in the PowerExchange CDC audit trail.

By default, this check box is selected.
Restart Token 1: This field is available only if you selected
CC
in the
Extract Type
field. If you want the database row test to start fetching data from a specific point in the change stream, enter a valid sequence token value in this field. The sequence token in combination with the restart token value in the
Restart Token 2
field identify the specific change record in the change stream from which the database row test will begin retrieving data. You can use these fields to bypass old records that have been archived off disk or to bypass records that are not consistent with an updated extraction map.
The sequence token is a binary value with a length that varies by data source type. You can generate a sequence token and restart token for the current end of the change stream in the following ways:

In the PowerExchange Navigator, perform a CAPXRT database row test that specifies the SELECT CURRENT_RESTART statement in the
SQL Statement
box. The
Database Row Test Output
window displays the generated token values.
Use the DTLUAPPL utility to generate the sequence token and restart token values. In the ADD or MOD APPL statement, include the RSTTKEN GENERATE parameter. Then use the PRINT APPL statement to print the generated token values.
The generated sequence token is in the format that is used by ODBC extractions. To use the token value for a database row test, add eight zeroes to the end of the value.

Alternatively, if you have run PWXPC CDC sessions recently, you can copy the token values from the following messages:

In the PowerExchange message log, the PWX-04565 and PWX-09959 messages show the sequence token in the
Sequence
field and the restart token in the
PowerExchange Logger
field
In the PowerCenter workflow session log, the PWXPC_12060 and PWXPC_12068 messages show the sequence token in the
Restart Token 1
field and the restart token in the
Restart Token 2
field. Also, the PWXPC_10081, PWXPC_10082, and PWXPC_12128 messages show the sequence token as the first token value and the restart token as the second token value.

If you need assistance with creating valid token values, contact Informatica Global Customer Support.
Restart Token 2: This field is available only if you selected
CC
in the
Extract Type
field. If you want the database row test to start fetching data from a specific point in the change stream, enter a valid restart token value in this field. The restart token value in combination with the sequence token value in the
Restart Token 1
field identify the specific change record in the change stream from which the database row test will begin retrieving data. You can use these fields to bypass old records that have been archived off disk or bypass records that are not consistent with an updated extraction map.
The restart token is a binary value with a length that usually varies by data source type. On z/OS, restart tokens for all data source types have the same length, except for change data extracted from full condense files. You can generate restart token and sequence token values that indicate the current end of the change stream from the PowerExchange Navigator or with the DTLUAPPL utility. Alternatively, if you have run PWXPC CDC sessions recently, you can copy the token values from messages in the session log or the PowerExchange message log. If you need assistance with creating valid token values, contact Informatica Global Customer Support.
Extraction Schema: Overrides the schema that is specified in the extraction map.
CAPI Connection Name: Overrides the default database connection that is defined in a CAPI_CONNECTION statement in the DBMOVER configuration file.

To point to the relevant data source, use the value that you defined in the NAME parameter of the CAPI_CONNECTION statement in the DBMOVER configuration file.

Required when multiple CAPI connection statements are included in the DBMOVER configuration file.
Extraction Map - Location: If you are extracting change data in continuous extraction mode from PowerExchange Logger for Linux, UNIX, and Windows log files that are remote from the extraction maps on the data source, enter the node name of the system where the extraction maps are located.

You must define this node in a NODE statement in the dbmover.cfg file where the PowerExchange Logger for Linux, UNIX, and Windows runs. Usually, this node name is the node name that you defined in the CAPTURE_NODE parameter in the pwxccl.cfg configuration file.

For example, if a PowerExchange Logger for Linux, UNIX, and Windows process captures change data from a remote IMS source on an z/OS system, specify the node name for the z/OS system.
Extraction Map - UserID: The user ID that is used to authorize PowerExchange Logger for Linux, UNIX, and Windows access to extraction maps on the remote node that is selected in the
Location
list.

Whether this user ID is required depends on the SECURITY setting in the DBMOVER configuration file at the remote location. This user ID can be either an operating system user ID or database ID, depending on the data source type.

Usually, this user ID is the one that you defined in the CAPTURE_NODE_UID parameter in the pwxccl.cfg configuration file.

For data sources on a supported Linux, UNIX, or Windows system, if you have enabled PowerExchange LDAP user authentication and, if applicable, disabled relational pass-through authentication, the user ID is the enterprise user name. For more information, see the
PowerExchange Reference Manual
.
Extraction Map - Password: A clear text password for the user ID that is specified in the
UserID
box. Usually, this value matches the CAPTURE_NODE_PWD parameter value in the pwxccl.cfg configuration file.

If you are using the PowerExchange Logger to access extractions maps that are on a remote i5/OS or z/OS node, you can enter a valid PowerExchange passphrase instead of a password. An i5/OS passphrase can be from 9 to 31 characters in length. A z/OS passphrase can be from 9 to 128 characters in length. A passphrase can contain the following characters:

Uppercase and lowercase letters

The numbers 0 to 9

Spaces

The following special characters:

’ - ; # \ , . / ! % & * ( ) _ + { } : @ | < > ?

The first character is an apostrophe.

Passphrases cannot include single quotation marks (‘), double quotation marks (“), or currency symbols.

On z/OS, the allowable characters in the IBM IRRPHREX exit do not affect the allowable characters in PowerExchange passphrases.

On z/OS, a valid RACF passphrase can be up to 100 characters in length. PowerExchange truncates passphrases longer than 100 characters when passing them to RACF for validation.

To use passphrases, ensure that the PowerExchange Listener runs with a security setting of SECURITY=(1,N) or higher in the DBMOVER member. For more information, see "SECURITY Statement" in the
PowerExchange Reference Manual
.

Click

to save changes. The source database connection closes. In the

Database Row Test

dialog box, click

to establish the database connection again and perform the database row test with the updated advanced properties.

Rename Saved Search

Table of Contents

Navigator User Guide

Navigator User Guide

CAPXRT Advanced Parameters Dialog Box - General Tab

CAPXRT Advanced Parameters Dialog Box - General Tab