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 the PowerExchange Listener JCL on z/OS

Configuring the PowerExchange Listener JCL on z/OS

PowerExchange provides PowerExchange Listener JCL in the following members of the RUNLIB library:
  • PWXLSTNR runs PowerExchange as a started task.
  • STARTLST runs PowerExchange as a batch job.
When you ran the XIZZZ998 job during installation, the PWXLSTNR member was copied to the PROCLIB library.
Review the PowerExchange Listener JCL before starting the PowerExchange Listener the first time.
To configure the PowerExchange Listener JCL on z/OS:
  1. Verify that the STEPLIB DD concatenation in the PowerExchange Listener JCL includes the load libraries for your source DBMSs.
    The STEPLIB concatenation in the STARTLST member includes the load libraries for all data sources in a proper order.
  2. Verify that the PARM statement specifies the node name that is defined in the LISTENER statement of the DBMOVER configuration file.
  3. In the REGION parameter of the EXEC statement, enter a region size. The region size indicates the amount of storage to allocate for running the PowerExchange Listener.
    The sample JCL specifies a region size of 384 MB in the EXEC statement.
    Informatica recommends a region size of 0M, which indicates that z/OS gives the job all the storage available below and above 16 megabytes. For important considerations about specifying a region size of 0M, see the
    z/OS MVS JCL Reference
    .
    If you omit the REGION parameter, the system default applies.
  4. Verify that the TIME parameter in the EXEC statement is set to NOLIMIT. The NOLIMIT setting enables the PowerExchange Listener job to run without a time limit and prevents timeout-related abends that might occur with abend code S322.
  5. If the SECURITY statement in the DBMOVER configuration file is set to 1 or 2, APF-authorize the PowerExchange LOADLIB library and any other load libraries in the STEPLIB DD concatenation of the PowerExchange Listener JCL.

0 COMMENTS

We’d like to hear from you!