Navigator User Guide

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

Back Next

Adding an Extraction Group

An extraction group is a named group of extraction maps.

An extraction group defines the data source instance, node location, and data source type. When you add a registration group, PowerExchange adds an extraction group with the same name. You can also manually add an extraction group as described in this procedure. Add extraction maps to the extraction group when you define the group or later.

On the

Resources

tab in the

Resource Explorer

, click

Add > Extraction Group

In the

Add Extraction Group

dialog box, enter the following information:

Name: A user-defined name for the extraction group. The maximum length is 16 characters.
Location: The location of the source for which you want to extract change data. Select
local
if the source is on the PowerExchange Navigator system.

This field lists the locations that are defined in NODE statements in the dbmover.cfg configuration file on the PowerExchange Navigator system.

Default is
local
.
Type: Data source type.

Select a data source type and enter the associated information, which must match the information in the corresponding registration group:

ADABAS
. Adabas files.

In the
Collection Identifier
box, enter the instance name.

AS4
. DB2 for i5/OS tables.

In the
Collection Identifier
box, enter the instance name specified in the INST parameter of the AS4J CAPI_CONNECTION statement in the DBMOVER member of the dtllib
/CFG file on the source system.

DATACOM
. CA Datacom/DB tables registered for CA Datacom/DB table-based CDC.

In the
MUF Name
box, enter the name of the source Multi-User Facility (MUF).

DB2
. DB2 for z/OS tables.

In the
Database Instance
box, enter the DB2 subsystem ID or the DB2 data-sharing group name.

DB2UDB
. DB2 for Linux, UNIX, and Windows tables.

In the
Database
box, enter the name of the database.

IDMS_L
. IDMS tables registered for IDMS log-based CDC.

In the
Registration Location
list, select the location where the capture registrations are to be stored.

In the
Source Map Location
list, select the location where the data maps for the IDMS tables are located.

In the
Logsid
box, enter the value specified in the LOGSID parameter in the DBMOVER configuration file on the source system.

IMS
. IMS databases.

For IMS synchronous CDC, in the
Recon Identifier
box, enter the IMS subsystem ID.

For IMS log-based CDC, in the
Recon Identifier
box, enter the value specified in the IMSID parameter in the DBMOVER configuration member on the z/OS system where the RECON data sets are located.

MSSql
. Microsoft SQL Server tables.

In the
Database Server
list, select the server where the source is located.

In the
Database Name
list, select or enter the name of the database.

ORACLE
. Oracle tables.

In the
Collection Identifier
box, enter the Oracle instance identifier specified in the ORACLEID statement in the DBMOVER configuration file on the source system.

VSAM
. VSAM ESDS, KSDS, RRDS, and VRRDS data sets.

In the
Collection Identifier
box, enter the instance name.
UserID: Enter a user ID that allows access to the source. The type of user ID depends on the source type and PowerExchange security settings:

If the source is on an i5/OS or z/OS system and PowerExchange security is enabled, enter an operating system user ID. PowerExchange security is enabled when the PowerExchange SECURITY statement in the DBMOVER member is set to (1,x) or 2.x).

For a DB2 for Linux, UNIX, and Windows, Microsoft SQL Server, or Oracle source, enter a valid database user ID, if required. For more information, see the SECURITY Statement in the
PowerExchange Reference Manual
.

For a source 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
.
Password: A password for the specified user ID.

If the source is on an i5/OS or z/OS system, 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 to128 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
.

If you specify a user ID but omit the password, when you open the extraction group, the PowerExchange Navigator prompts you for the password in the
Missing Password
dialog box.
Add Extraction Definition: Adds extraction maps to the group.

Clear this option to add only the extraction group.

Default is selected.