Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Bulk Data Movement
  3. PowerExchange Listener
  4. Adabas Bulk Data Movement
  5. Datacom Bulk Data Movement
  6. DB2 for i5/OS Bulk Data Movement
  7. DB2 for Linux, UNIX, and Windows Bulk Data Movement
  8. DB2 for z/OS Bulk Data Movement
  9. IDMS Bulk Data Movement
  10. IMS Bulk Data Movement
  11. Microsoft SQL Server Bulk Data Movement
  12. Oracle Bulk Data Movement
  13. Sequential File Bulk Data Movement
  14. VSAM Bulk Data Movement
  15. Writing Data with Fault Tolerance
  16. Monitoring and Tuning Options

Bulk Data Movement Guide

Bulk Data Movement Guide

Setting Up and Testing Connectivity to a Remote DB2 Source or Target

Setting Up and Testing Connectivity to a Remote DB2 Source or Target

If the DB2 data source or target is on a remote system, PowerExchange and PowerCenter must be able to communicate with the PowerExchange Listener on that remote system.
To set up and test connectivity to a remote DB2 source or target:
  1. 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 system with the DB2 source or target.
  2. Add the NODE statement to the dbmover.cfg file on each PowerExchange and 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.
  3. 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.

0 COMMENTS

We’d like to hear from you!