Bulk Data Movement Guide

10.5
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

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.

If the SECURITY statement is set to 0 or 1 in the DBMOVER configuration member, edit the following specifications on the JOB card in the DB2LDJCL or DB2LDJCP template member:

Remove or change the value of the NOTIFY parameter. Otherwise, the load job may fail.

Remove the USER and PASSWORD parameters. Otherwise, the load job will fail.

Also, to identify the name of the reject data set, which PowerExchange allocates dynamically, edit the JCL that defines the data set. The skeleton JCL that is provided in DB2LDJCL defines the data set as follows:

//SYSDISC  DD  UNIT=SYSDA,SPACE=(CYL,(100,100),RLSE)

For example, you can replace the JCL above with the following JCL:

 //SYSDISC DD DISP=SHR,DSN=%REJECT

This example defines a reject data set with the name &HLQ.
taskid
.REJECT.

If the DB2 bulk files are uploaded with "NOSUBMIT", %REJECT is resolved to $HLQ.REJECT, not $HLQ.taskid.REJECT.

To include the output from a failed DB2 LOAD job and the name of the reject data set in the PowerCenter session log, specify RETLOGINFOMSG=Y in the PWX Override connection attribute. The name of the reject data set appears in the PWX-00409 message.

Rename Saved Search

Table of Contents

Bulk Data Movement Guide

Bulk Data Movement Guide

Customizing the PowerExchange Templates for Bulk Data Loads

Customizing the PowerExchange Templates for Bulk Data Loads