CDC Guide for Linux, UNIX, and Windows

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

Back Next

Example of Remote Logging from a z/OS Data Source

In this example, you use a PowerExchange Logger for Linux, UNIX, and Windows instance on a UNIX system to relog change data for Db2 for z/OS data sources. The system where the PowerExchange Logger runs is separate from the PowerCenter Integration Service system where you run the CDC sessions.

The PowerExchange Logger for z/OS captures change data for registered Db2 for z/OS tables and logs that data to its log files on the z/OS system. The PowerExchange Logger for Linux, UNIX, and Windows reads data from the PowerExchange Logger for z/OS log files and relogs that data on the UNIX system. PowerCenter CDC sessions then extract change data from the PowerExchange Logger for Linux, UNIX, and Windows log files rather than from the log files on the z/OS source system.

You need the PowerExchange Logger for Linux, UNIX, and Windows to read change data for registered tables in the Db2 instance DSN9 and then relog that data to its log files on the remote UNIX system. To do so, you must customize a PowerExchange Logger for Linux, UNIX, and Windows configuration file on the UNIX system and dbmover configuration files on both the z/OS and UNIX systems. Also, for the PowerCenter CDC sessions to extract change data from the PowerExchange Logger log files on UNIX, you must add NODE statements for the source and PowerExchange Logger systems to the dbmover configuration file on the Integration Service system and configure some PWXPC connection attributes.

First install PowerExchange on all three systems. You must run a PowerExchange Listener on the source system and on the PowerExchange Logger system. A PowerExchange Listener is not required on the PowerCenter Integration Service system.

On the z/OS source system, ensure that the DBMOVER member in the RUNLIB library includes the following CAPI_CONNECTION statements:

LISTENER=(MVS02,TCPIP,2480)
/* UOW Cleanser
CAPI_CONNECTION=(NAME=MV2UOWC,TYPE=(UOWC,CAPINAME=M2_LRAP,RSTRADV=600,MEMCACHE=20480,DATACLAS=UOWC))
/* Log Read API Connection
CAPI_CONNECTION=(NAME=MV2_LRAP,TYPE=(LRAP,LOG=MV2L,AGENT=MV2A))

On the UNIX system with the PowerExchange Logger for Linux, UNIX, and Windows log files, ensure that the dbmover configuration file includes the following statements:

/*
/* dbmover 
/*
LISTENER=(unix1,TCPIP,2480)
NODE=(MVS02,TCPIP,prodmvs2,2480)
...
LOGPATH=/pwx/logs/mvscond
CAPT_XTRA=/pwx/capture/mvscond/camaps
CAPT_PATH=/pwx/capture/mvscond
/*
/* Source-specific CAPI Connection
CAPI_CONNECTION=(NAME=MV2UOWC,TYPE=(UOWC,CAPINAME=M2_LRAP,RSTRADV=600,MEMCACHE=20480))
CAPI_CONNECTION=(NAME=MV2_LRAP,TYPE=(LRAP,LOG=MV2L,AGENT=MV2A))
/*
/* CAPX CAPI Connection for continuous extraction
CAPI_CONNECTION=(NAME=CAPXDSN9,TYPE=(CAPX,DFLTINST=DSN9,FILEWAIT=60,RSTRADV=600))

In the CAPX CAPI_CONNECTION, the DFLTINST value is the name that is displayed in the

Instance

field for the registration group in the PowerExchange Navigator.

On the UNIX system with the PowerExchange Logger system log files, customize the PowerExchange Logger for Linux, UNIX, and Windows configuration file, pwxccl.cfg. For this example, include the following statements:

/*
/* pwxccl 
/*
DBID=DSN9 
DB_TYPE=DB2
CONN_OVR=MV2UOWC
CAPTURE_NODE=MVS02
PROMPT=Y
EXT_CAPT_MASK=/pwx/capture/mvscond/condense 
COND_CDCT_RET_P=50 
LOGGER_DELETES_EXPIRED_CDCT_RECORDS=Y 
COLL_END_LOG=0 
NO_DATA_WAIT=0
NO_DATA_WAIT2=10  
FILE_SWITCH_VAL=20000 
FILE_SWITCH_CRIT=R 
CAPT_IMAGE=BA

The CAPTURE_NODE parameter points to the source system node where the PowerExchange Listener processes capture requests.

Start the PowerExchange Listener and PowerExchange Logger for Linux, UNIX, and Windows on the UNIX system. Verify that the PowerExchange Listener is also running on the z/OS system.

On the PowerCenter Integration Service system, add the following NODE statements to the dbmover file:

A NODE statement that points to the PowerExchange Listener on the source system

A NODE statement that points to the PowerExchange Listener on the UNIX system with the PowerExchange Logger log files, if you not using a "local" connection

This example uses the following NODE statements in the dbmover file on the PowerCenter Integration Service machine:

NODE=(unix1,TCPIP,unix1,2480)
NODE=(MVS02,TCPIP,prodmvs2,2480)

Create a PowerCenter mapping, session, and workflow.

Configure a PWX DB2zOS CDC Real Time application connection for the CDC sessions that extract change data from the PowerExchange Logger log files on the UNIX system.

For this example, set the following connection attributes:

For the

Location

attribute, enter unix1 to point to the node where the PowerExchange Logger for Linux, UNIX, and Windows log files reside. CDC sessions will read data from this location.

For the

Map Location

attribute, enter MVS02 to point to the location of the extraction maps, which the z/OS source system node.

For the

Map Location User

attribute, enter a valid user ID for the map location.

For the

Map Location Password

attribute, enter the password for the map location user.

For the

CAPI Connection Name

attribute, enter CAPXDSN9 to indicate the CAPX CAPI_CONNECTION statement to use.

Cold start the CDC session.

The session begins extracting change data from the PowerExchange Logger log files on the UNIX system.

Remote Logging of Data

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal

1 COMMENTS

Back Next

We’d like to hear from you! Log in to comment.

Rodrigo Dos Santos - May 12, 2024

Where it says: "For the Location attribute, enter unix2 to point to the node where the PowerExchange Logger for Linux"

it should say: "For the Location attribute, enter unix1 to point to the node where the PowerExchange Logger for Linux"

Informatica Documentation Team - May 13, 2024

Updated and published to the Doc Portal.

Rename Saved Search

Table of Contents

CDC Guide for Linux, UNIX, and Windows

CDC Guide for Linux, UNIX, and Windows

Example of Remote Logging from a z/OS Data Source

Example of Remote Logging from a z/OS Data Source