ADA

for Adabas

AS4

for DB2 for i (i5/OS)

DB2

for DB2 for z/OS

DCM

for Datacom

IDL

for IDMS log-based

IMS

for IMS

MSS

for Microsoft SQL Server

MYS

for MySQL

ORA

for Oracle

PGS

for PostgreSQL

UDB

for DB2 for Linux, UNIX, and Windows

VSM

for VSAM

For

ADA

, enter an Adabas nucleus name.

For

AS4

, enter a DB2 for i (i5/OS) instance value that matches the INST parameter value in the AS4J CAPI CONNECTION statement in the DBMOVER member of the

dtllib

/CFG file. If you use PowerExchange Condense, this instance value must also match the DBID parameter value in the CAPTPARM member.

For

DB2

, enter a DB2 subsystem ID (SSID).

For

DCM

, enter a Datacom Multi-User Facility (MUF) name.

For

IDL

, enter an IDMS log-based CDC instance value that matches the

registration_logsid

parameter in the LOGSID statement in the DBMOVER configuration member.

For

IMS

, enter an IMS subsystem ID that matches the

ims_ssid

parameter value in the IMSID statement in the DBMOVER configuration member.

For

MSS

, optionally enter a unique user-defined instance identifier for the SQL Server database server and database name combination defined in the MSSOPTS DBSERVER and DBNAME parameters. Maximum length is seven characters. This identifier is incorporated into the names of the extraction maps that the utility creates. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this instance value, PowerExchange generates a unique instance identifier that is composed of all or part of the publication database name followed by a 3-digit number if a number is required to make the identifier unique.

This INSTANCE parameter is useful in migration scenarios. If you need to deploy change capture from one environment to another, such as from test to production, and you do

not

define an instance identifier, PowerExchange uses the generated instance identifier in the new environment. The generated instance identifier might be different than the one in the original source environment. To avoid having to update the extraction map names in PowerCenter workflows and edit the DBID parameter value for the PowerExchange Logger, enter an instance identifier in the INSTANCE parameter that matches the instance identifier in the original environment when creating registrations for the new environment.

For

MYS

, enter a unique, user-defined instance identifier for the MySQL database server. Maximum length is seven characters. This identifier is used to identify a set of registrations for tables in the database on the MySQL server. This identifier is also incorporated into the names of the extraction maps that the utility creates. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that this instance identifier matches the DBID parameter value in the Logger configuration file.

For

ORA

, enter the user-defined collection ID for the Oracle instance that matches the

collection_id

parameter in the ORACLEID statement in the PowerExchange DBMOVER configuration member.

For

PGS

, enter a unique, user-defined instance identifier for the PostgreSQL database server and database name combination defined in the PGSOPTS DBSERVER and DBNAME parameters. Maximum length is seven characters. This identifier is incorporated into the names of the extraction maps that the utility creates. If you use the PowerExchange Logger for Linux, UNIX, and Windows, ensure that the instance identifier matches the DBID parameter value in the Logger configuration file. If you do not enter this instance value, PowerExchange generates a unique instance identifier that is composed of all or part of the database name followed by a three-digit number.

For

UDB

, enter a DB2 for Linux, UNIX, and Windows database name.

For

VSM

, enter a VSAM collection identifier.