ADACMP Utility Messages

#### Search Results

Search

# ADACMP Utility Messages

### Overview of Messages

`ERROR-121 | ERROR-122 | ERROR-123 | ERROR-124 | ERROR-125 | ERROR-126 | ERROR-127 | ERROR-128 | ERROR-129 | ERROR-130 | ERROR-131 | ERROR-132 | ERROR-133 | ERROR-135 | ERROR-136 | ERROR-137 | ERROR-138 | ERROR-139 | ERROR-140 | ERROR-141 | ERROR-142 | ERROR-143 | ERROR-144 | ERROR-145 | ERROR-148 | ERROR-149 | ERROR-150 | ERROR-151 | ERROR-152 | ERROR-153 | ERROR-154 | ERROR-155 | ERROR-156 | ERROR-157 | ERROR-158 | ERROR-159 | ERROR-161 | ERROR-162 | ERROR-163 | ERROR-164`

ERROR-121 | Invalid value for parameter RECFM
Explanation | This parameter is required for z/VSE only. Valid values are:
RECFM=F | fixed
RECFM=FB | fixed blocked
RECFM=V | variable
RECFM=VB | variable blocked
RECFM=U | undefined
Action | Supply the correct parameter value and rerun the job.

ERROR-122 | Missing function code
Explanation | One of the keywords COMPRESS or DECOMPRESS must be specified.
Action | Supply the required function keyword to the input and then rerun the job.

ERROR-123 | Missing field definition table (FDT)
Explanation | The parameter input must contain either the field definition table or the parameter "FDT=file-number".
Action | Add a valid FDT parameter, and then rerun the job.

ERROR-124 | Error reading field definition table (FDT)
Explanation | The nucleus returned response code nn while reading the field definition table (FDT). "response" is the nucleus response.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-125 | Invalid value for parameter `UTYPE'
Explanation | Valid values are UTYPE=EXU or UTYPE=EXF.
Action | Supply the correct parameter value, and then rerun the job.

ERROR-126 | Invalid input data set
Explanation | The input data set (EBAND/DDEBAND) must have a record format of variable or variable blocked.
Action | Supply a correct input data set and rerun the job.

ERROR-127 | Syntax / semantic error found during field definition table (FDT) compilation
Explanation | ...cause of message displayed here... Some of the causes are: an SQL null field (NC) was specified with the NU (null suppression) option, or for a fixed-point (FI) field type. a multiple-value (MU) field or an occurrence in a periodic (PE) group was specified as an SQL null value (NC option) field. more than 254 elementary fields were defined in the specified (`xx') periodic (PE) group.
Action | Correct the field definition table (FDT) definition, and then rerun the job.

ERROR-128 | Invalid value for the parameter `CODE'
Explanation | The value specified for the CODE parameter is either incorrect, or the CODE parameter is not valid in this case.
Action | Either remove the CODE parameter, or specify at most eight digits, or blanks. Rerun the job. Refer to the Adabas Security documentation for more information.

ERROR-129 | The supplied format buffer is wrong
Explanation | "FORMAT=xxxxxxxx" or "FORMAT=**" is incorrect.
Action | Specify a correct value for format, and then rerun the job.

ERROR-130 | Hyperexit not loaded
Explanation | The hyperdescriptor exit number nnnn has not been defined to ADACMP.
Action | Add the HEXnn parameter to the ADARUN input, and rerun the job. The HEX parameter nn defines the hyperdescriptor exit to ADACMP.

ERROR-131 | Invalid value for the `SORTSEQ' parameter
Explanation | The following values are allowed:
SORTSEQ=ISN | to process an ISN sequence.
SORTSEQ=DE | where DE is any descriptor whose parent field is not an MU field or contained in a periodic group; that is not a phonetic descriptor or hyperdescriptor and does not have the NU option.
Action | Supply the correct parameter value, and rerun the ADACMP job.

ERROR-132 | Descriptor desc-name for file file-number has the `NU' option
Action | Select another descriptor, or add the parameter NU to the utility input. In this case, records may be lost. See the ADACMP utility description in the Adabas Utilities documentation for more information.

ERROR-133 | Parameter ETID not allowed
Explanation | The ADACMP utility ETID parameter may only be specified if the INFILE parameter is also specified.
Action | Check the parameter input, correct any incompatibility or other error, and then rerun the job.

ERROR-135 | Incorrect FDT found in input data set
Explanation | One of the following is the case: the field definition table (FDT) expected in the first record is missing, or the FDT structure 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-136 | Parameter error
Explanation | At least one of the parameters UACODE, UWCODE, FACODE, FWCODE, or FWUCODE contains an invalid value. Valid encoding values are 0-4095.
Action | Correct the encoding key value and rerun the job.

ERROR-137 | Parameter error
Explanation | The architecture key parameter UARC contains an invalid value. Valid values are 0-11.
Action | Correct the architecture key value and rerun the job.

ERROR-138 | UES object object failed to load
Explanation | The required UES object specified was not loaded. It is likely that the object does not exist in the UES data set.
Action | Locate the required object and load it.

ERROR-139 | UES internal error
Explanation | This error usually results when at least one required UES object is missing.
Action | Determine which object(s) is missing and reload it.

ERROR-140 | UES initialization failed
Explanation | Additional error messages follow that indicated the source of the error.
Action | Correct the problem and rerun the job.

ERROR-141 | UACODE/UWCODE/UARC specified, but no FACODE/FWCODE specified or implied
Explanation | The utility does not have access to the nucleus information about the file. You must specify all values.
Action | Either remove the user encoding values (UACODE/UWCODE/UARC) or specify the file encoding values (FACODE/FWCODE) as well.

ERROR-142 | Wide field detected but length uneven
Explanation | The length must be a multiple of the wide character size without a remainder to accommodate only full characters. For example, when using a three-byte character size, the length must be evenly divisible by 3; for a four-byte character size, the length must be evenly divisible by 4.
Action | Correct the problem and rerun the job.

ERROR-143 | Wide field detected but FUCODE not specified
Explanation | Wide fields must specify code page information; that is, a wide-character field encoding such as FWCODE=4095 (Unicode).
Action | Correct the problem and rerun the job.

ERROR-144 | Invalid ET-ID
Explanation | When running DECOMPRESS on a multiclient file, Adabas processes either the entire file if ET-ID is not specified; or the selection of records allowed for the client identified by ET-ID. The user ID referred to by the `ETID' parameter is either not defined or has not been assigned an owner ID.
Action | Investigate the cause of the error; correct it; and rerun the job.

ERROR-145 | Invalid spanned record encountered Input record count = count
Explanation | An ADACMP DECOMPRESS run encountered an invalid spanned compressed record in the input.
Action | Contact your Software AG support representative for assistance.

ERROR-148 | DDFEHL record length too small Must be at least 500 bytes
Explanation | The DDFEHL error data set must have a record length of at least 500 bytes to accommodate the ADAF header and the initial logical record segment.
Action | Assign a larger sequential record length to the DDFEHL data set and try again.

ERROR-149 | MAXLOGRECLEN less than minimum Must be at least 32768 bytes
Explanation | The value specified for the MAXLOGRECLEN parameter is too small; it must be at least 32768 bytes.
Action | Supply the correct parameter value and then rerun the job.

ERROR-150 | HEADER=YES but first input record does not have a valid ADAH header
Explanation | The HEADER parameter was set to "YES" for an ADACMP COMPRESS run, but the first uncompressed input record does not have a valid ADAH header.
Action | Review the input records and determine whether the input records are in error or whether the HEADER parameter should be set to "NO" instead. if the problem persists, contact your Software AG support representative for assistance.

ERROR-151 | DDAUSBA record length too small Must be at least number bytes
Explanation | The DDAUSBA data set record length is too small for ADACMP DECOMPRESS processing. If the HEADER parameter is set to "NO", the minimum length is the length of the record descriptor word (RDW) plus one byte. if the HEADER parameter is set to "YES", the minimum length is the length of the RDW plus the length of the ADAH or ADAC header plus one byte.
Action | Assign a larger sequential record length to DDAUSBA and try again.

ERROR-152 | DDAUSB1 record length too small. Must be at least nnn bytes.
Explanation | The DDAUSB1 data set record length is too small for COMPRESS with LOBVALUES=YES. The record length must be large enough to accommodate the compressed record length determined by the LOBDEVICE parameter and control information.
Action | Assign a larger sequential record length to DDAUSB1 or reevaluate the LOBDEVICE parameter setting. Then try again.

ERROR-153 | Code specified but LOB fields exist for file
Explanation | The CODE parameter is not supported for files containing large object (LB option) fields.
Action | Specify a different file or remove the CODE parameter and try again.

ERROR-154 | LOBVALUES=YES but no LOB fields exist for file.
Explanation | The LOBVALUES parameter should only be set to YES for input files that have large object (LB) fields.
Action | Investigate the cause of the error and try again.

ERROR-155 | LOBVALUES=YES with DECOMPRESS requires INFILE.
Explanation | The ADACMP DECOMPRESS function that specifies LOBVALUES=YES requires that the INFILE parameter be set to the base file of a LOB file group in order to populate the LOB values in the uncompressed records.
Action | Specify an INFILE parameter and try again.

ERROR-156 | Decompress of a LOB file is not permitted.
Explanation | You cannot run the ADACMP DECOMPRESS function on a LOB file. It can only be specified on the base file of a LOB file group.
Action | Ensure the input file is specified correctly and is not a LOB file and try again.

ERROR-157 | Invalid LOB information detected for file filenum
Explanation | The ADACMP DECOMPRESS INFILE with LOBVALUES=YES did not detect a valid LOB file. Either no LOB file is associated with the base file referenced in the message (filenum) or the LOB file information in the base file is invalid.
Action | Ensure the specified base file is properly associated to a LOB file and try again.

ERROR-158 | Error during hyperexit call A call to hyperexit number nn resulted in a response 79 with subcode code
Explanation | A hyperdescriptor exit call failed with response code 79 (ADARSP079) and the subcode given in the message.
Action | Investigate the subcode to determine the reason for the error.

ERROR-159 | Invalid LOB field specification in FORMAT parameter
Explanation | The FORMAT parameter contains an invalid LB (large object) field specification.
Action | Review the restrictions for specifying LB fields in the FORMAT parameter with LOBVALUES=NO. Correct the FORMAT parameter and rerun the job.

ERROR-161 | The DST parameter also requires the TZ parameter
Explanation | If you specify the DST parameter, you must also specify a valid TZ parameter.
Action | Supply the correct parameter values and rerun the job.

ERROR-162 | The TZ parameter is required when the FDT has a field with the TZ option
Explanation | A field with the TZ option was found in the FDT, but the TZ parameter was not specified in the ADACMP run.
Action | Supply the correct parameter values and rerun the job.

ERROR-163 | The time zone specified by the TZ parameter is invalid
Explanation | An invalid time zone value was specified in the TZ parameter. The time zone specified must be a valid time zone name contained in the TZINFO member of the Adabas time zone library (ADAvrs.TZ00). Adabas uses the time zone data taken from the tz database, which is also called the zoneinfo or Olson database. The specific list of time zone names that Adabas supports in any given release can be found in the TZINFO member of the Adabas time zone library (ADAvrs.TZ00). For more information about the TZINFO member of the time zone library, read Supported Time Zones.
Action | Supply a valid parameter value and rerun the job.

ERROR-164 | FACODE should be an EBCDIC type and a Single Byte Coding System Check supplied UES Encodings.
Explanation | A code system specified in the FACODE parameter is not known or is not EBCDIC or is not a single-byte encoding system.
Action | Check the documentation section Supplied UES Encodings in the Adabas User, Hyperdescriptor, Collation Descriptor, and SMF Exits Manual for the valid code and correct the job parameter accordingly.