ERROR_THRESHOLD

Most pointer errors that are encountered during a reorganization or unload process will prevent processing of the area and will terminate the process.

Certain pointer errors can be bypassed and allow processing to continue.

The ERROR_THRESHOLD keyword can be used to enable the primary command process to encounter and bypass a specified number of pointer errors without terminating. The ERROR_THRESHOLD keyword is used to specify the number of pointer errors that can be bypassed in the processing of an area before terminating the process.

When ERROR_THRESHOLD is used with the UNLOAD command, the database record is written up to the point of the segment in error, and processing continues with the next accessible segment. The segment containing the pointer error (and its dependent segments) is bypassed and is not written to the unload file. When the number of errors encountered in all database records that have been read exceeds the value specified on the ERROR_THRESHOLD keyword, processing of the area terminates.

When ERROR_THRESHOLD is used with the REORGANIZE command, any UOW where a pointer error is detected is bypassed (not reorganized), and processing continues with the next eligible UOW. When the number of UOWs where errors are encountered exceeds the value specified on the ERROR_THRESHOLD keyword, processing of the area terminates.

Use

ERROR_THRESHOLD is an optional keyword for the following commands:

CHANGE
RELOAD
REORGANIZE
UNLOAD

Related keyword

SDEP_PROCESS

Warning

When you specify SDEP_PROCESS=PHYSICAL on the UNLOAD command, the process does not read SDEPs by following pointers. Consequently, pointer errors in the SDEP portion of the database will not be detected. If you want the ERROR_THRESHOLD keyword to detect and bypass any pointer errors detected in the SDEP portion of the DEDB, then you must specify SDEP_PROCESS=LOGICAL.

Syntax

ERROR_THRESHOLD=parameter

Parameters

Specify a value from 0 to 99999.

Default

ERROR_THRESHOLD=0

Alias

ERT