ADAMER Utility Messages

#### Search Results

Search

# ADAMER Utility Messages

### Overview of Messages

`ERROR-122 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-130 | ERROR-131`

ERROR-122 | Incorrect FDT found in input data set
Explanation | The structure of the FDT read from the input data set does not satisfy the rules.
Action | Check whether the input data set is valid. Supply a correct input data set and rerun the job.

ERROR-124 | Invalid value for the parameter ADAMDE
Explanation | The name of the ADAM descriptor was not found in the FDT.
Action | Supply ADAMDE=ISN or ADAMDE=xx, where "xx" is any valid descriptor name. Then rerun the job.

ERROR-125 | Invalid ADAMDE field: xx
Explanation | Conflicting field attributes or unknown descriptor name. An ADAM descriptor must be a single field (no MU option); be a unique descriptor; not be contained in a periodic group; not have the NU option; have a default length (cannot be variable).
Action | Supply the correct parameter value and rerun the job.

ERROR-126 | Invalid value for the parameter BITPARM
Explanation | See the Adabas Utilities documentation for further information.
Action | Supply the correct parameter value and rerun the job.

ERROR-127 | Data Storage size too small
Explanation | The amount of Data Storage to store the records is greater than the data size parameter.
Action | Supply the correct parameter value and rerun the job.

ERROR-130 | Input data set has spanned records. ADAM files may not be spanned.
Explanation | The input data set has spanned record support active. The spanned record option is not allowed for ADAM files.
Action | Check whether the input data set is valid. Supply a correct input data set and rerun the job.

ERROR-131 | Input data set is a LOB file. ADAMER is not allowed for LOB files.
Explanation | The input data set is a large object (LOB) file. LOB files may not be input to ADAMER.
Action | Check whether the input data set is valid. Supply a correct input data set and rerun the job.