The VALIDATE function validates the contents of the Data Storage against the values in the Associator. This is done by issuing commands to create a DVT that is validated against each corresponding value in the indices.
Note:
ADAVAL VALIDATE cannot be performed on the checkpoint or security
files.
This document covers the following topics:
FILE specifies a one or more Adabas file numbers and/or file ranges. A maximum of 1000 files may be specified.
Continuation for a file list is as follows:
ADAVAL VALIDATE FILE=1-10,15 ADAVAL FILE=13,31-35
ADAVAL will concatenate the file list for each specification of the FILE parameter.
SORTSIZE specifies the number of blocks or cylinders available for the sort dataset. If specifying blocks, the value must be followed by "B" (for example, 2000B). A block value is automatically "rounded up" to the next full cylinder. See the Adabas DBA Reference documentation for information about estimating the SORTSIZE value.
TEMPSIZE specifies the number of blocks or cylinders available for the temp dataset. If specifying blocks, the value must be followed by "B" (for example, 2000B). A block value is automatically "rounded up" to the next full cylinder. See see the section LOAD File Space Allocation in the ADALOD description for information about estimating the TEMPSIZE value.
The CODE parameter is required if the file or file(s) being validated are enciphered.
The DESCRIPTOR parameter restricts validation processing to one descriptor field, providing a way to limit the validation run in cases where that the Associator is very large or there is a need to evaluate a specific descriptor. If DESCRIPTOR is not specified, ADAVAL validates all qualifying descriptor fields.
The following is an example of DESCRIPTOR use:
ADAVAL VALIDATE FILE=5,DESCRIPTOR='AA,CC,BB'
LPB specifies the size, in bytes, of the internal prefetch buffer. The maximum value is 32760 bytes. The default depends on the current ADARUN LU value. ADAVAL VALIDATE may reduce the LPB value below that specified if the LU value is too small.
LRECL specifies the maximum length of all descriptor values in any record of the file being validated. This length is used by ADAVAL to create a temporary record buffer. If the LRECL value is too small, response code 53 occurs when an oversized record is found. The default for LRECL is 4000 bytes; the maximum length allowed is 32760 bytes.
LWP specifies the size of the work pool to be used for descriptor value sorting. The value can be specified in bytes or kilobytes followed by a "K". If no value is specified, the default is 1048576 bytes (or 1024K); however, to shorten ADAVAL run time for files with very long descriptors or an unusually large number of descriptors, set LWP to a higher value. To avoid problems with the Sort dataset, a smaller LWP value should be specified when validating relatively small files.
The minimum work pool size depends on the Sort dataset's device type:
| Sort Device | Minimum LWP | Minimum LWP |
|---|---|---|
| Bytes | Kilobytes | |
| 2000 | 106496 | 104K |
| 2314 | 090112 | 88K |
| 3375 | 131072 | 128K |
| 3380 | 139264 | 136K |
| 3390 | 159744 | 156K |
When an error is encountered while the function is running, the utility prints an error message and terminates with user abend 34 (with a dump) or user abend 35 (without a dump).
If NOUSERABEND is specified, the utility will not abend after printing the error message. Instead, the message "utility TERMINATED DUE TO ERROR CONDITION" is displayed and the utility terminates with condition code 20.
This parameter is required if the file or file(s) to be validated are password-protected.
The SORTDEV parameter indicates the device type to be used for the sort dataset that ADAVAL uses to sort descriptor values (the sort dataset size is specified with SORTSIZE). This parameter is required only if the device type to be used is different from that specified by the ADARUN DEVICE parameter.
The TEMPDEV parameter indicates the device type to be used for the temp dataset that ADAVAL uses to store intermediate data. The dataset size is specified with the TEMPSIZE parameter. This parameter is required only if the device type to be used is different from that specified by the ADARUN DEVICE parameter.
