Bulk Data Movement Guide

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

Back Next

Setting Up and Testing Connectivity to a Remote DB2 for z/OS Source or Target

To access DB2 bulk data on a remote z/OS system, PowerExchange must be able to communicate with the PowerExchange Listener on the remote system.

To set up and test connectivity to a remote DB2 for z/OS source or target:

On the systems where the PowerExchange Navigator, PowerCenter Client, and PowerCenter Integration Service run, use the ping
command to test network access to the remote MVS system with the DB2 source or target.

Add the NODE statement to the dbmover.cfg file on each PowerExchange or PowerCenter system to identify the remote PowerExchange Listener and its port:

NODE=(node_name,TCPIP,ipaddress_or_hostname,port_number)

To determine the port number, consult with the person in your organization who installed the PowerExchange Listener on the remote system.

Run the DTLREXE ping utility on the local PowerExchange system to test connectivity to the remote PowerExchange Listener that you defined in the NODE statement.

Configuring DB2 for z/OS Bulk Data Movement

Managing the PowerExchange Listener

Download Guide

Watch

Comments

Communities

Knowledge Base

Success Portal