Create a new server for Db2/z - Connect_CDC - connect_cdc_mimix_share - 6.x

Connect CDC Getting Started Guide
Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
6.x
Language
English
Product name
Connect CDC
Title
Connect CDC Getting Started Guide
Copyright
2024
First publish date
2003
Last updated
2024-10-15
Published on
2024-10-15T20:38:41.117981

This section describes how you create a new server for Db2/z.

  1. On the Servers Properties dialog select Db2/z from the drop-down list in the DBMS type section.

  2. Enter information for each field on the Server Properties dialog. Refer to Server for field information.

Table 1. Server Properties dialog for DB2/z

Parameter

Description

Name

A unique server name to use in the model. If the server is remote, the name must be the machine name that is used by Connect CDC to make the remote connection.

Note: The slash (/), backslash (\), colon (:), left caret (<), right caret (>) and spaces cannot be used in a server name.

DBMS Type

Select DB2/z from the drop-down list.

Location name

The unique name requesters use to connect to the DB2 subsystem. The value of the DB2 Location name field must be the same on all members within a DB2 data sharing group.

DBMS instance port

The port assigned on the DB2 subsystem to accept DBMS requests.

JDBC Driver

Select a driver from the drop-down. The default is DB2ZOS.

Driver Version

View the JDBC Driver version. This information is obtained each time a connection to the database is made, including a Test Connection. (Informational only)

DBMS logon IDs and DBMS logon password
Specify the Default and Rep user IDs.

  1. Input the user login ID for accessing this DB2 subsystem.

  2. Specify the owner of the metabase on this DB2 subsystem.

  3. Select Default and Rep user (they may be different).

  • The Default user is what Connect CDC Director uses to connect to the server.

  • The Rep user is what the kernel uses to connect to the server.

Note: When adding, updating, or deleting rows on the source table, do not use the replication user ID to make these changes. Changes made by the replication user are ignored by change capture triggers.
Specify additional IDs.

  1. In DBMS logon password, enter the logon password for the ID.

  2. In DBMS logon IDs, for the second user ID, select Type in a new ID.

  3. Specify an ID that can access and query the source or target tables on this DB2 subsystem for testing or informational purposes.

    Note: Do not select Default or Rep user.

  4. Specify the ID password in DBMS logon password.

Remote Machine Name or IP

Select this check-box if you are creating a new remote location for DB2/z. Specify the remote machine name or IP address. The remote machine name or IP address must be a valid machine name or IP address of the machine hosting the remote DB2/z subsystem The remote machine name (or IP address), and the location name establish the connection with the remote location. This is a required field.

 

Capture tab

Parameter

Description

Capture Info

  

Server

The name of the z/OS server that hosts capture agent. Often, the value you enter here is the same as the location name of the system where DB2 subsystem is installed.

Port

The port assigned on the z/OS server to accept CDC Capture requests.

Agent

The name of the CDC Capture Agent installed on z/OS. After entering the server and port information, choose “Refresh” to automatically fill in the names of any active Capture Agents names on the z/OS server.

Private key path

Name and path of the private key file used to authenticate Capture connections with the Capture daemon running on z/OS.

JCL Info

  

Job card

The JCL Job statement, which schedules CDC extract jobs on z/OS.

Job Lib

The JCL DD statement identifying the LOADLIB path where DMXDC is installed on the z/OS system required to run the JCL job. z/OS only searches public libraries if none are set in Job Lib.

ISPF Lib

Path to DMXCDC ISPF libraries.