DBD control statement

The DBD control statement identifies the database to be scanned. Only one DBD control statement can be used.


DBDdbname  index   sednnn  b
Code the DBD keyword to identify the DBD control statement.
Code the DBD name.

Code the name of the DBD that describes the physical database to be scanned. This required 8-character field must be left-aligned with trailing blanks. The DBD must specify ACCESS=HDAM, HIDAM, PHDAM, PHIDAM, HISAM, or SHISAM.

Code the index name.

The 8-character entry is optional and valid only for running in the ULU region. This entry specifies the name of index DBD that is either the primary index of the HIDAM database or a secondary index of the HIDAM or HDAM database if you want the root segments to be retrieved in the index sequence. For details, see Considerations for using a secondary index.

Code this field to activate the sequence check option.

This 1-character entry s determines whether to perform sequence check during the unload processing. Specify one of the following keywords:

Perform sequence checking.
N | blank
Do not perform sequence checking (default).
Code this field to activate the sequence error option.

The 1-character entry e determines whether the output routines bypass or process sequence errors. Specify one of the following keywords:

A | blank
Accept sequence errors (default). A GX status code is returned.
Bypass sequence errors. The segment in error, and all of its children, are skipped. A GG status code is returned.
Code this field to activate the sequence error print option.

The 1-character entry d determines whether diagnostic information is printed for sequence errors in the HSSRTRAC data set. Specify one of the following keywords:

Y | blank
Print diagnostic data on sequence errors (default).
Do not print diagnostic data.
Code this field to specify the sequence error threshold.

The 3-digit numeric entry nnn indicates the number of sequence errors to be allowed before ending the run (the default value is 10). Any number up to 999, with leading or trailing blanks, can be used. If you use the number 999, sequence errors do not cause the run to end.

Code this field to activate the pointer bypass option.

The 1-character entry b is used to activate the pointer bypass option. The pointer bypass option allows FABHFSU to continue processing a database that contains bad pointers, instead of issuing an abend. The pointer bypass option automatically activates the DIAGG option.

Specify one of the following keywords:

The pointer bypass option is inactive.
This entry invokes the pointer bypass option.
This entry forces FABHFSU to use the index, rather than the root twin forward pointers, to unload an HIDAM or PHIDAM database.
See Utility options for unloading corrupted databases, for instructions and considerations for using the pointer bypass option.