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

Configuring PowerExchange for Bulk Data Movement with a DL/1 Batch Data Map

Configuring PowerExchange for Bulk Data Movement with a DL/1 Batch Data Map

Use the following procedure to set up PowerExchange for bulk data movement operations that use a DL/1 Batch data map and a netport job. A netport job can run either as an IMS DL/I Batch or BMP job.
To configure PowerExchange for bulk data movement with a DL/1 batch data map:
  1. Create one or more netport jobs for accessing IMS metadata. Use the sample netport job in the IMSJCL member of the RUNLIB library as a template. Customize this member so that it runs in your environment as either a DL/I Batch or BMP job.
  2. In the DBMOVER configuration member on the MVS system where the IMS database is located, uncomment and customize the LISTENER and NETPORT statements for the IMSJCL member. Use the following syntax:
    LISTENER=(node_name,TCPIP,port_number) NETPORT=(node_name,port_number,,,"hlq.RUNLIB(ims_netport_member)",psb_id)
    Where:
    • node-name
      is a name that you define for the PowerExchange Listener that runs on the IMS source or target system. Specify the same node name in both the LISTENER and NETPORT statements. Also, define a NODE statement that contains the same node name in the dbmover.cfg file on the Windows system or systems on which you run the PowerExchange Navigator and PowerCenter Integration Service.
    • port_number
      is a valid port number at your site. To get a valid port number, consult with your network administrator. Specify the same port number in both LISTENER and NETPORT statements.
    • psb_id
      is a valid IMS PSB identifier for the IMS source or target.
    • hlq
      .RUNLIB.
      ims_netport_member
      is the fully-qualified data set name and member name for the member where the IMS netport job is stored. You created this member based on the sample IMSJCL member.
    Restriction
    : You must run the specified PowerExchange Listener and netport job on the same MVS image. Otherwise, the netport job fails.
    If you plan to move bulk data for multiple PSBs, enter a pair of LISTENER and NETPORT statements for each PSB.
  3. Restart the PowerExchange Listener after you finish making changes to the DBMOVER configuration member.

0 COMMENTS

We’d like to hear from you!