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 PowerExchange Templates for Bulk Data Loads

Customizing the PowerExchange Templates for Bulk Data Loads

You can use the JCL and control card templates without modification if you accept the default JCL statements and control cards for the DB2 LOAD utility. Alternatively, you can edit these templates to change the control cards or to use other load utilities.
The RUNLIB data set contains the default DB2LDJCL or DB2LDJCP template member. Make sure that the
JCL Template
attribute refers to this member in the connection.
In the JCL, substitution variables begin with a percent sign (%). Before submitting the DB2 LOAD job to z/OS, PowerExchange resolves defined substitution variables with the appropriate values. For more information, seeSubstitution Variables in the Loader JCL Templates.
If the SECURITY statement is set to 2 in the DBMOVER configuration member, make sure to include USER=%USER and PASSWORD=%PWD in the JCL.
You can retain discarded update records for a short time by changing the SYSDISC DD in the JCL from:
//SYSDISC DD UNIT=SYSDA,SPACE=(CYL,(100,100),RLSE)
to:
//SYSDISC DD DISP=SHR,DSN=%SYSDISC
This edited statement creates the discards file with a name in the format
HLQ.basename.SYSDISC
.
The base name derives from the task ID. The next DB2 LOAD utility job that runs in the same task slot overwrites the discards file.
Informatica recommends that the DB2 LOAD utility control report from the SYSPRINT file be written to the session log of the caller. To write the SYSPRINT file to the session log, set RETLOGINFOMSG=Y in the
PWX OVERRIDE
connection attribute.
For more information about DD statement requirements for the DB2 LOAD utility, see the IBM DB2 documentation.

0 COMMENTS

We’d like to hear from you!