The DIGITCHECK option allows you to verify that an explicitly or implicitly required NUMBER item contains only digits during a STORE operation. If a NUMBER item with DIGITCHECK set contains a nondigit hexadecimal (leading signs of 4"C" and 4"D" are allowed), a DATAERROR 01 exception is returned.
The DIGITCHECK option is reset by default.
This option is useful when a database is transported between different enterprise servers. When a NUMBER item, which is stored as a packed decimal, contains nondigits, the value of the same data can be different for different enterprise servers under certain circumstances. This difference in values can occur when a NUMBER item is specified as a DESCENDING key. Using the DIGITCHECK option guarantees that NUMBER items contain only correctly formed packed decimal values.
If the NULL value of the NUMBER item is not the default value or the high value, you might need to perform extra checking when the data is stored.
If the DIGITCHECK option is set in <data set physical options>, all explicitly or implicitly required NUMBER items in that data set are examined. It is set for the data set by specifying DIGITCHECK or DIGITCHECK = TRUE.
If a data set designates the DIGITCHECK option, all remaps of that data set inherit the DIGITCHECK option.
| Note: | The DIGITCHECK option can be set for the entire database. Refer to Using the Defaults Specification, for additional information. If conflicting values are specified for this option, the conflict is resolved in the following order: |
-
Value specified at the item level (highest)
-
Value specified at the data set level
-
Value specified at the database level
Refer to “Using the REQUIRED Keyword” earlier in this section for information about required items.
