How do I choose which load utility will be used when loading records in batch?

Document ID : KB000020820
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

After data has been extracted from it's source location the next step is to use the Target Definition to load it to the target location.

RC/Extract is able to do this using an SQL or a Utility load. If a Utility load is selected then this can only be executed in batch and there is a choice between CA Fast Load for DB2 for z/os or the IBM DB2 Load Utility.

Solution:

The selection of the Utility type to be used when generating JCL for batch execution is found in the RC/Extract PROFILE
2 - RC/Extract Profile Variables, RC/Extract Parameters
Load Utility ===> PFL ( IBM or PFL )

This profile variable can be changed by each user whenever required to change utility type before JCL for a load should be generated.

The profile can be accessed from the main RC/Extract menu "P PROFILE" or by using the PROFILE option line command.

Changes to this PROFILE option also causes dynamic changes in the RC/Extract Update Load Parms options available at the "Process Target Definition" screen since the two utilities have different features.

Depending on which one is used(PFL or IBM) in the PROFILE these Load parms are available:

RC/Extract FAST LOAD Options
 
 Load Resume/Replace ==> N          (Y - Yes or N - No or R - Replace    )
 MAPDDN Error log    ==> Y          (Y/N, Y = SYSMAP DD for error info   )
 Save discarded rows ==> Y          (Y/N, Y = Alloc SYSDISC error dataset)
 ALLMSGS Messages    ==> N          (Y/N, Y = additional error message   )
 Max discard rows    ==> 0          (Max errors allowed, 0 = no limit    )
 
 IGNORE THE MARKED ERRORS DURING THE LOAD  ==> Y
   01. VARCHAR TOO LARGE    ==> N    02. DATA VALUE TOO LARGE   ==> N
   03. DATA NOT NUMERIC     ==> N    04. DATA FIELD TOO LARGE   ==> N
   05. INVALID DATA FOUND   ==> N    06. DATE FIELD INVALID     ==> N
   07. TIME FIELD INVALID   ==> N    09. INVALID GRAPHICS DATA  ==> N
   15. DUPLICATE INDEX KEY  ==> N    16. INDEX KEY SEQUENCE ERR ==> N
   18. FAILED FIELDPROC     ==> N    19. FAILED VALIDPROC CHECK ==> N
   20. FAILED OBID CHECK    ==> N    21. FAIL CONDITIONAL CHECK ==> N
   22. FAILED PARTITION KEY ==> N   100. FAILED WHEN SELECTION  ==> Y
 
IBM LOAD UTILITY OPTIONS:
 
 Load Resume/Replace  ==> N   (Y - Yes, N - No, or R - Replace               )
 Log data             ==> N   (Y/N - Y = Data is logged as loaded            )
 SORTKEYS             ==> N   (Y/N - Y = Keys sorted as loaded  V5 and Above )
   Number of keys     ==> 0           (Estimated number of keys V5 and Above )
 Enforce constraints  ==> N   (Y/N - Y = Enforce system RI constraints       )
 SYSERR Error log     ==> Y   (Y/N - Y = Error info logged to SYSERR         )
 MAPDDN Error log     ==> Y   (Y/N - Y = SYSMAP DD for error information     )
 Save discarded rows  ==> Y   (Y/N - Y = allocate SYSDISC error dataset      )
 Max discard rows     ==> 0            ( Max errors allowed, 0 = no limit    )