DISCARDS

The default is 0 (no limit) when you do not specify the DISCARDS keyword. When you specify the DISCARDS keyword, you must supply a value and this value must be an integer (which can be 0).

You can also specify a user-defined return code for LOADPLUS to use when you reach this limit. (See IFDISCARDLIMIT.)

Additional considerations

The following considerations apply to this option:

• When invoking DSNUTILB, LOADPLUS passes this option to the IBM Db2 LOAD utility for processing.
• Unless you are running an SQLAPPLY load job, this option is not valid for a single-phase load (PRELOAD LOAD) when you specify LOAD RESUME YES.

• For a two-phase load, a value greater than 0 for this option is meaningful only with one of the following options:

  • UNIQUECHECK YES (which is the default)
  • UNIQUECHECK CLUSTER when all participating unique indexes are data-sorting indexes

  For information, see UNIQUECHECK.

Discard violations

Discard violations are calculated as the total number of violations that cause LOADPLUS to discard input records during the PRELOAD or COMBINED phase for a particular load job. For example, if two input records are duplicates and they both violate a check constraint, LOADPLUS reports four discard violations (assuming that you did not specify IGNORE DUPKEY or IGNORE CHKC). In this case, however, the SYSDISC data set contains only the two discarded input records.

LOADPLUS generates discard violations for any of the following reasons:

• An input value position is past the end of the input record.
• An input value is not entirely contained in the input record.
• A data conversion error (including a FIELDPROC error) occurs.
• A value generated for an identity column is out of range.
• A verification record does not match the table that is being loaded (FORMAT BMCUNLOAD).
• LOADPLUS encounters an error byte during data translation.
• LOADPLUS encounters a substitution character during data translation, but you specified NOSUBS.
• An expansion error occurs during data translation.
• A VALIDPROC violation occurs.
• A record does not match any WHEN specification or table OBID.
• A record does not match any partition that is being loaded.
• A Db2 check constraint violation occurs.
• A Db2 referential constraint violation occurs.
• An informational referential constraint violation occurs (and INFORI is YES).
• A unique key violation occurs in the PRELOAD or COMBINED phase.
• An SQLCODE -330, -530, or -803 occurs during an SQLAPPLY load.
• A problem occurs with a referenced file that is used to load LOB or XML data.
• A problem occurs with an XML document.
• A conversion error occurs on a key that is derived from an expression.

Records in the cases described in the following table are discarded but not recorded as discard violations. The discarded records are not written to the discard data set, and they do not count toward the DISCARDS limit.

The IGNORE option tells LOADPLUS to ignore the specified discard types during the PRELOAD phase or the COMBINED phase. If the specified type of discard occurs, LOADPLUS

• Does not write an error record to the SYSERR data set (unless the discard is a duplicate key error or referential constraint violation)
• Does not report the error in the error summary report (unless the discard is a referential constraint violation)
• Does not write the corresponding input record to the discard data set (unless the record also violates another discard type)

An ignored discard violation does not count toward the DISCARDS limit.

The IGNORE option is especially useful for WHEN and PART discards when all records in your input file do not participate in the load.

The following table lists the keywords and discards types, along with their descriptions, that you can specify with the IGNORE option:

Restriction

This option is not valid when LOADPLUS invokes DSNUTILB. LOADPLUS issues message BMC50178E and terminates.

REPORT

The REPORT option tells LOADPLUS which discard types to report or not report in the error summary report. Although this option has no effect on actual discard processing, it allows you to limit the number of SYSPRINT records when you expect many discards.

Restriction

When invoking DSNUTILB, LOADPLUS ignores this option.