ADASEL Error Messages

An end-of-file was reached on the DD/KARTE dataset before ADASEL expected to reach an end-of-file. Most likely, the supplied input statements are incomplete.

See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statements, then rerun the ADASEL job.

The input string marked by " <---- " does not match the ADASEL syntax.

See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statement syntax, then rerun the ADASEL job.

The value specified by the SET GLOBALS parameter, LST, does not define an ADASEL translation table large enough for all the statements that match the SELECT argument.

Specify a SET GLOBALS statement with an LST value larger than the current specified or default value. The SET GLOBALS statement must come before the other ADASEL input statements. See the Adabas Utilities documentation for more information.

The input string marked by " <---- " is longer than 253 bytes.

Correct the string length, then rerun the ADASEL job.

ADASEL detected an uneven number of apostrophes ('). All alphanumeric and hexadecimal values must be specified in pairs of apostrophes; apostrophes in an alphanumeric string must be doubled (as in `...don' 't forget...')

Ensure that all specified apostrophes are paired, then rerun the ADASEL job.

A binary value in an ADASEL search criterion must be in the range of a two's complement value that fits within a fullword. The value specified was not recognized to be within this range.

Correct the value specification and rerun the ADASEL job.

The ADASEL syntax elements must be embedded in blanks.

See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statement syntax, then rerun the ADASEL job.

Hexadecimal values must be paired, and be valid characters.

See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statement syntax, then rerun the ADASEL job.

Adabas generally does not allow unpacked decimal values longer than 29 bytes.

Supply a correct numeric value of 29 or fewer packed characters, then rerun the ADASEL job.

The specified numeric value for the ADASEL criterion is invalid.

Check the criterion specification, and then rerun the ADASEL job.

The ADASEL table allocated for evaluating field values is not large enough.

Specify a larger table value by using the SET GLOBALS statement parameter, NV. The SET GLOBALS statement must come before the other ADASEL input statements. See the Adabas Utilities documentation for more information.

An internal error occurred while ADASEL was checking the input statement syntax.

Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

The specified file number(s) for FILE must be greater than zero and equal to or less than the value last specified by the MAXFILES parameter in the ADADEF DEFINE utility.

Ensure that the defined file(s) are correct according to MAXFILE, that the specified files actually exist and that no files have been deleted.

The allowed number of files for ADASEL processing was exceeded.

Specify a larger file table value by using the SET GLOBALS statement parameter NF. The SET GLOBALS statement must come before the other ADASEL input statements. See the Adabas Utilities documentation for more information.

One or more of the specified files is not available for ADASEL processing. The unavailable file(s) are either locked by the Adabas nucleus, or have not been loaded into the database.

Either correct the ADASEL FILE specification to remove the files in question, or resubmit the job later when the files are available.

The "starting from" and "ending at" date/time specification was incorrect. The format may be any one of the following:

      
        yyyymmdd/hhmmss
        
          
        

        J(yyyyddd
        

        hhmmss)
        
          
        

        X'
        xxxx xxxx

        '
      
    

Correct the date/time specification and rerun the ADASEL job.

The specified ADASEL fieldname is incorrect, or does not exist.

Specify a correct fieldname, then rerun the ADASEL job.

A field was specified for ADASEL that is not an elementary field, or the index value for a periodic group field was forgotten. Multiple-value and periodic group names, super-, sub-, hyper- or phonetic descriptor fields are not allowed.

Respecify the field correctly, then rerun the ADASEL job.

A periodic group field was specified for ADASEL with an incorrect or invalid index value, which must be in the range of 1-191.

Specify the correct index value and rerun the ADASEL job.

A periodic group's field or multiple-value field's occurrence contained an illegal hyphen in the index portion of the specification.

Correct the specification and rerun the ADASEL job.

An index value or range was specified for a field that is neither in a periodic group nor an occurrence in an multiple-value field.

Remove the index value from the field specification, or correct the field name to show a periodic group or multiple-value field.

A multiple-value field was specified for ADASEL with an incorrect or missing index value, which must be in the range of 1-191.

Specify the correct index value and rerun the ADASEL job.

The "FROM" index specification for a multiple-value (MU) or periodic group (PE) field for the ADASEL job is greater than the "TO" index specification.

Specify correct index value(s) and rerun the job.

A field was defined for ADASEL that is in floating-point format. Floating point fields cannot be specified in an ADASEL search argument.

Respecify the ADASEL search argument using non-floating-point field name(s).

An alphanumeric value was specified without being enclosed in apostrophes ([X]'...').

Correct the value specification and rerun the ADASEL job.

An incorrect ADASEL criterion value range was specified.

Correct the EQUAL ..., THRU ...(through ...), and/or BUT NOT... values and rerun the ADASEL job.

The field selected by the ADASEL criterion is defined with the fixed-length (FI) option, but the value specified for the field is longer than allowed by the field's FDT definition.

Correct the value size and rerun the ADASEL job.

The number of "nested" IF levels in the ADASEL IF/THEN [ELSE] statement is more than allowed. The number of IF... levels is controlled by the ADASEL SET GLOBALS/NIF parameter.

Specify a larger IF... count by using the SET GLOBALS statement parameter NIF. The SET GLOBALS statement must come before the other ADASEL input statements. See the Adabas Utilities documentation for more information.

ADASEL detected an IF... without an ELSE..., or vice versa. IF... and ELSE... conditional parameters must occur in pairs.

Correct the ADASEL IF/ELSE syntax to create paired conditional parameters, and rerun the job.

ADASEL detected a DO... statement without a matching DOEND..., or vice versa.

Correct the ADASEL DO...DOEND syntax to create DO...DOEND pairs, and rerun the job.

The ADASEL output dataset(s) DD/EXPAn was either not numbered or incorrectly numbered. There must be at least one output dataset (DD/EXPA1), up to a maximum of twenty, numbered in adjoining ascending order (DD/EXPA1, DDEXPA2, ... DD/EXPA20).

Correct the DD/EXPAn job control statement(s), and rerun the ADASEL job.

The "yyyy" portion of the date specified by the ADASEL input statement must be "1980" or later.

Correct the date and rerun the ADASEL job.

The table for field evaluations in ADASEL is too small. Each "evaluation" of a field requires one table entry-regardless of whether only one field is evaluated many times or many fields, one time each.

Specify a larger field evaluation table value by using the SET GLOBALS statement parameter, NV. The SET GLOBALS statement must come before the other ADASEL input statements. See the Adabas Utilities documentation for more information.

A DD/ASSORn job control statement for the ADASEL job specified an incorrect or undefined Associator device type. The default device type is the type specified by the ADARUN DEVICE parameter, but other device types may have been specified for the Associator. The ADAREP utility report or Adabas Online System "Database Report" function shows the devices in use for the Associator.

Correct the DD/ASSORn job control statement, and rerun the ADASEL job.

The ADASEL "SELECT..." specification is incorrect. The choices are before image (BI), after image (AI), or ALL.

Correct the SELECT specification, then rerun the ADASEL job.

The ADASEL FILE... specification specified an invalid file number. There is no FDT for a file with the specified number.

Correct the SELECT specification, then rerun the ADASEL job.

An ADASEL criterion specified invalid EQUAL... and/or THRU (through)... ISN values.

Correct the SELECT specification, then rerun the ADASEL job.

An input/output error occurred while ADASEL was reading the DD/KARTE input statements.

Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

ADASEL encountered a record that could not be decompressed.

Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

ADASEL detected an invalid SET GLOBALS statement value. The SET GLOBALS statement, which should come before the ADASEL parameters themselves, overrides default values for the ADASEL parameters.

Correct the SET GLOBALS statement in the ADASEL DD/KARTE job control segment, and rerun the ADASEL job. See the Adabas Utilities documentation for more information.

The ADASEL job could not be run in the existing space.

Allocate more space for this nucleus, then rerun the ADASEL job.

ADASEL detected an incorrect multiple-value field count or periodic group occurrence, or a field value was specified that is incompatible with the defined field's actual length. ADASEL could not continue processing.

Correct the incompatibility, then rerun the ADASEL job.

The table for evaluating periodic-group (PE) fields in ADASEL is too small. ADASEL normally computes this size automatically; however, there may have been more occurrences matching the search criterion than normal.

Specify a larger PE field evaluation table value by using the SET GLOBALS statement parameter, LPV. The SET GLOBALS statement must come before the other ADASEL input statements. See the Adabas Utilities documentation for more information.

ADASEL was unable to open the DD/KARTE input statement dataset.

Ensure that the DD/KARTE statement is valid and specifies an available ADASEL job setup. Then rerun the ADASEL job.

The DD/DRUCK job control statement, which specifies the print output dataset for ADASEL, is either incorrect or specifies an unavailable dataset or device.

Correct the problem and rerun the ADASEL job.

An ADASEL IF... statement cannot be within a DO...DOEND stream.

Move the IF... statement outside the DO...DOEND stream, or delete one of them. Then rerun the ADASEL job.

ADASEL detected an invalid SET GLOBALS parameter value. The value is most likely outside the range allowed for the parameter. The following are some SET GLOBAL parameters and their allowed ranges:

Correct the SET GLOBALS statement in the ADASEL DD/KARTE job control segment, and rerun the ADASEL job. See the Adabas Utilities documentation for more information.

The DD/SIIN job control statement, which specifies the sequential input (SIBA) log dataset for ADASEL, is either incorrect or specifies an unavailable dataset or device. Another possible cause is that the DD/SIIN dataset is not the sequential output file from an ADARES COPY/PLCOPY operation, as required by ADASEL.

Correct the problem and rerun the ADASEL job.

The DD/EXPA job control statement, which specifies the print output dataset for ADASEL, is either incorrect or specifies an unavailable dataset or device.

Correct the problem and rerun the ADASEL job.

While decompressing a file, ADASEL detected a record that it could not decompress.

Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

ADASEL cannot be run on ciphered files.

Change the file specification to exclude all ciphered files, then rerun the ADASEL job.

The CHANGES option requires both a before (BI) and after (AI) image for comparison following an update (A1/4) command. Either the BI or AI image was not available.

Remove the CHANGES parameter from the ADASEL syntax.

The default values of 10 (the count of "field-name" CHANGES... statements) for the NCFLD and NCUPD SET GLOBALS parameters of the ADASEL job are not large enough. These two counts are multiplied to determine the correct value.

Increase one or both of the NCFLD and NCUPD parameters in the SET GLOBALS statement of the ADASEL DD/KARTE job, and rerun the ADASEL job. See the Adabas Utilities documentation for more information.

The IF "field-name" CHANGES... conditional statement of an ADASEL job specified a multiple-value (MU) field value or periodic group (PE) occurrence index value that does not exist, or that has no before (BI) and after (AI) image. The field value or group occurrence may have been added or deleted, eliminating one of the required images.

The IF...CHANGES... conditional statement cannot be specified in this case. Redefine the ADASEL statement.

While decompressing a file, ADASEL detected a record that it could not decompress. The "reason-code" tells you why:

Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

The PLOG was created by an Adabas cluster nucleus and has not yet been merged using the ADARES PLCOPY procedure.

Merge the PLOGs using the ADARES PLCOPY function before you extract data using ADACDC.