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

Customizing the DBMOVER Configuration Member for the DB2 LOAD Utility

Customizing the DBMOVER Configuration Member for the DB2 LOAD Utility

In the DBMOVER configuration member, set statements to identify the libraries that contain the PowerExchange JCL and control card templates for the DB2 LOAD utility.
The following table describes these statements:
Statement
Description
Default
LOADJOBFILE
Name of PDS library that contains the JCL template for bulk data movement jobs that use the DB2 LOAD utility.
Default is the PowerExchange RUNLIB library.
The default template member name is DB2LDJCL.
LOADCTLFILE
Name of PDS library that contains the control card template for bulk data movement jobs that use the DB2 LOAD utility.
Default is the PowerExchange RUNLIB library.
The default template member name is DB2LDCTL.
Review the following considerations for other DBMOVER configuration member statements:
  • PC_AUTH=Y.
    If you specify PC_AUTH=Y in the DBMOVER member of the PowerExchange Listener, you cannot run bulk load operations under the control of that PowerExchange Listener. Instead, use a netport job that specifies a DBMOVER member without this statement to run bulk load operations.
  • MVSDB2AF=RRSAF.
    If you specify MVSDB2AF=RRSAF, specify
    JOB
    for
    Mode Type
    in the PWX DB2zOS relational connection parameters to run the bulk load operation as a separate batch job. To run bulk load operations as tasks in the PowerExchange Listener address space, you must specify MVSDB2AF=CAF.
  • SUBMITTIMEOUT.
    If the PowerExchange Listener submits batch jobs for bulk load operations, verify that the value of the SUBMITTIMEOUT statement provides sufficient time for the batch job to start execution.
  • MAXTASKS.
    If you use netport jobs for bulk load operations, verify that the value of the MAXTASKS statement is sufficient. Each bulk load operation run with a netport job uses three tasks from the MAXTASKS value.

0 COMMENTS

We’d like to hear from you!