ADASEL Utility Messages

#### Search Results

Search

# ADASEL Utility Messages

### Overview of Messages

`SEL001 | SEL002 | SEL003 | SEL004 | SEL005 | SEL006 | SEL007 | SEL008 | SEL009 | SEL010 | SEL011 | SEL012 | SEL013 | SEL014 | SEL015 | SEL016 | SEL017 | SEL018 | SEL019 | SEL020 | SEL021 | SEL022 | SEL023 | SEL024 | SEL025 | SEL026 | SEL027 | SEL029 | SEL030 | SEL031 | SEL032 | SEL033 | SEL034 | SEL035 | SEL036 | SEL037 | SEL038 | SEL039 | SEL040 | SEL041 | SEL043 | SEL044 | SEL045 | SEL046 | SEL047 | SEL048 | SEL049 | SEL050 | SEL051 | SEL052 | SEL053 | SEL054 | SEL055 | SEL056 | SEL057 | SEL058 | SEL059 | SEL060 | SEL061 | SEL062 | SEL063 | SEL065 | SEL066 | SEL067 | SEL068 | SEL069 | SEL075 | SEL076 | SEL077 | SEL078 | SEL079 | SEL080 | SEL081 | SEL082 | SEL084 | SEL085 | SEL086 | SEL087 | SEL088 | SEL089 | SEL090 | SEL091 | SEL092 | SEL093 | SEL094 | SEL096 | SEL097 | SEL098 | SEL099 | SEL100 | SEL101 | SEL102 | SEL103 | SEL104 | SEL105 | SEL106 | SEL108 | SEL109 | SEL133`

SEL001 | Unexpected end-of-file on DDKARTE
Explanation | An end-of-file was reached on the DD/KARTE data set before ADASEL expected to reach an end-of-file. Most likely, the supplied input statements are incomplete.
Action | See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statements, then rerun the ADASEL job.

SEL002 | Syntax - undefined, illegal or incorrect syntax positioning of a parameter or symbol
Explanation | The input string marked by " <---- " does not match the ADASEL syntax.
Action | See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statement syntax, then rerun the ADASEL job.

SEL003 | Statement table overflow - increase LST
Explanation | 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.
Action | 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.

SEL004 | Syntax - value length exceeds the maximum field definition limit
Explanation | The input string marked by " <---- " is longer than 253 bytes.
Action | Correct the string length, then rerun the ADASEL job.

SEL005 | Syntax - unexpected or missing quote
Explanation | 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...')
Action | Ensure that all specified apostrophes are paired, then rerun the ADASEL job.

SEL006 | Syntax - a numeric value specified for a binary field must be -2 147 483 648 < VAL < 2 147 483 647
Explanation | 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.
Action | Correct the value specification and rerun the ADASEL job.

SEL007 | Syntax - missing trailing blank
Explanation | The ADASEL syntax elements must be embedded in blanks.
Action | See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statement syntax, then rerun the ADASEL job.

SEL008 | Syntax - illegal hex digit or an odd number of hex digits were specified
Explanation | Hexadecimal values must be paired, and be valid characters.
Action | See the ADASEL syntax description in the Adabas Utilities documentation. Correct the input statement syntax, then rerun the ADASEL job.

SEL009 | Syntax - numeric value contained more than 29 digits
Explanation | Adabas generally does not allow unpacked decimal values longer than 29 bytes.
Action | Supply a correct numeric value of 29 or fewer packed characters, then rerun the ADASEL job.

SEL010 | Syntax - illegal numeric value
Explanation | The specified numeric value for the ADASEL criterion is invalid.
Action | Check the criterion specification, and then rerun the ADASEL job.

SEL011 | Value table overflow - increase NV
Explanation | The ADASEL table allocated for evaluating field values is not large enough.
Action | 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.

SEL012 | Internal logic failure - contact your local Adabas support representative
Explanation | An internal error occurred while ADASEL was checking the input statement syntax.
Action | Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

SEL013 | Invalid file number. File number must be 0<FNR<=MAXFILES (as specified for the database)
Explanation | 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.
Action | Ensure that the defined file(s) are correct according to MAXFILE, that the specified files actually exist and that no files have been deleted.

SEL014 | File table overflow - increase NF
Explanation | The allowed number of files for ADASEL processing was exceeded.
Action | 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.

SEL015 | No FDT read due to absent or inaccurate ASSO data set or because the file is not loaded
Explanation | 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.
Action | Either correct the ADASEL FILE specification to remove the files in question, or resubmit the job later when the files are available.

SEL016 | Syntax - invalid DATE/TIME value specified
Explanation | 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'
Action | Correct the date/time specification and rerun the ADASEL job.

SEL017 | Syntax - password/cipher value length exceeds 8 characters or digits
Explanation | The password/cipher specified for the ADASEL run had an incorrect length.
Action | Correct the password/cipher value and rerun the ADASEL job.

SEL018 | Syntax - undefined or illegal field name
Explanation | The specified ADASEL fieldname is incorrect, or does not exist.
Action | Specify a correct fieldname, then rerun the ADASEL job.

SEL019 | Syntax - field name specified is not an elementary (name) a group or PE (periodic) - group name is not permitted
Explanation | 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.
Action | Respecify the field correctly, then rerun the ADASEL job.

SEL020 | Syntax - invalid periodic index specified (must be 0 < PE <= 191)
Explanation | A periodic group field was specified for ADASEL with an incorrect or invalid index value.
Action | Specify the correct index value and rerun the ADASEL job.

SEL021 | Syntax - illegal hyphen specified in an index
Explanation | A periodic group's field or multiple-value field's occurrence contained an illegal hyphen in the index portion of the specification.
Action | Correct the specification and rerun the ADASEL job.

SEL022 | Syntax - an index is specified for a non1-indexable field name; i.e., not an MU- or PE-field
Explanation | 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.
Action | Remove the index value from the field specification, or correct the field name to show a periodic group or multiple-value field.

SEL023 | Syntax - missing or illegal MU-index
Explanation | A multiple-value field was specified for ADASEL with an incorrect or missing index value.
Action | Specify the correct index value and rerun the ADASEL job.

SEL024 | Syntax - 'FROM' index value is > 'TO' index value
Explanation | 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.
Action | Specify correct index value(s) and rerun the job.

SEL025 | Syntax - fields defined with a format of float are not permitted to be specified
Explanation | A field was defined for ADASEL that is in floating-point format. Floating point fields cannot be specified in an ADASEL search argument.
Action | Respecify the ADASEL search argument using non-floating-point field name(s).

SEL026 | Syntax - missing quote(s) for an alphameric value
Explanation | An alphanumeric value was specified without being enclosed in apostrophes ([X]'...').
Action | Correct the value specification and rerun the ADASEL job.

SEL027 | Internal logic failure - contact your local Adabas support representative
Explanation | An internal logic error occurred during ADASEL processing.
Action | Record and save all output from the job, your input statements, and any dump. Then contact your Software AG technical support representative for assistance.

SEL029 | Syntax - illegal FROM/THRU/BUT NOT value specified; i.e., EQUAL > THRU or BUT NOT > THRU, etc
Explanation | An incorrect ADASEL criterion value range was specified.
Action | Correct the EQUAL ..., THRU ...(through ...), and/or BUT NOT... values and rerun the ADASEL job.

SEL030 | Syntax - value length exceeds the fixed length defined for this field
Explanation | 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.
Action | Correct the value size and rerun the ADASEL job.

SEL031 | Syntax - maximum number of IF - levels exceeded. Increase NIF
Explanation | 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.
Action | 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.

SEL032 | Syntax - Unmatched IF/ELSE statements
Explanation | ADASEL detected an IF... without an ELSE..., or vice versa. IF... and ELSE... conditional parameters must occur in pairs.
Action | Correct the ADASEL IF/ELSE syntax to create paired conditional parameters, and rerun the job.

SEL033 | Syntax - Unmatched DO/DOEND statements
Explanation | ADASEL detected a DO... statement without a matching DOEND..., or vice versa.
Action | Correct the ADASEL DO...DOEND syntax to create DO...DOEND pairs, and rerun the job.

SEL034 | Syntax - DDEXPA data set number specified - must be 1 - 20 inclusive
Explanation | The ADASEL output data set(s) DD/EXPAn was either not numbered or incorrectly numbered. There must be at least one output data set (DD/EXPA1), up to a maximum of twenty, numbered in adjoining ascending order (DD/EXPA1, DDEXPA2, ... DD/EXPA20).
Action | Correct the DD/EXPAn job control statement(s), and rerun the ADASEL job.

SEL035 | Syntax - The year specified in the date must be 1980 or later
Explanation | The "yyyy" portion of the date specified by the ADASEL input statement must be "1980" or later.
Action | Correct the date and rerun the ADASEL job.

SEL036 | Field description table overflow - increase NV
Explanation | 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.
Action | 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.

SEL037 | An undefined ASSO device type was specified. Check the ADARUN DEVICE parameter
Explanation | 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.
Action | Correct the DD/ASSORn job control statement, and rerun the ADASEL job.

SEL038 | Invalid TYPE value specified, must be AI/BI/ALL
Explanation | The ADASEL "SELECT..." specification is incorrect. The choices are before image (BI), after image (AI), or ALL.
Action | Correct the SELECT specification, then rerun the ADASEL job.

SEL039 | Invalid file number specified
Explanation | The ADASEL FILE... specification specified an invalid file number. There is no FDT for a file with the specified number.
Action | Correct the SELECT specification, then rerun the ADASEL job.

SEL040 | Invalid or illegal FROM/THRU ISN values specified
Explanation | An ADASEL criterion specified invalid EQUAL... and/or THRU (through)... ISN values.
Action | Correct the SELECT specification, then rerun the ADASEL job.

SEL041 | I/O error on DDKARTE
Explanation | An input/output error occurred while ADASEL was reading the DD/KARTE input statements.
Action | Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

SEL043 | Table overflow - too many values specified
Explanation | ADASEL encountered a record that could not be decompressed.
Action | Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

SEL044 | Syntax - invalid or illegal GLOBAL parameter
Explanation | 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.
Action | 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.

SEL045 | Unable to obtain sufficient memory for processing - rerun in a larger partition or address space
Explanation | The ADASEL job could not be run in the existing space.
Action | Allocate more space for this nucleus, then rerun the ADASEL job.

SEL046 | Unable to process Data Storage record due to an invalid MU/PE - count or field length or header
Explanation | 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 or an incorrect record's header. ADASEL could not continue processing.
Action | Correct the incompatibility, then rerun the ADASEL job.

SEL047 | PE-value table overflow - increase LPV
Explanation | 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.
Action | 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.

SEL048 | DDKARTE open failed
Explanation | ADASEL was unable to open the DD/KARTE input statement data set.
Action | Ensure that the DD/KARTE statement is valid and specifies an available ADASEL job setup. Then rerun the ADASEL job.

SEL049 | I/O error on DDDRUCK
Explanation | The DD/DRUCK job control statement, which specifies the print output data set for ADASEL, is either incorrect or specifies an unavailable data set or device.
Action | Correct the problem and rerun the ADASEL job.

SEL050 | Error during opening/closing of output file DDEXPA
Explanation | ADASEL was unable to open/close the data set defined in JCL statement DD/EXPA.
Action | Ensure that the DD/EXPA statement is valid and specifies an available data set. Then rerun the ADASEL job.

SEL051 | Syntax - IF statement not permitted within a DO-group
Explanation | An ADASEL IF... statement cannot be within a DO...DOEND stream.
Action | Move the IF... statement outside the DO...DOEND stream, or delete one of them. Then rerun the ADASEL job.

SEL052 | Syntax - GLOBAL parameter exceeds the MINIMUM/MAXIMUM values
Explanation | 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:
LS: | 1-132
PS: | 2-999
Action | 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.

SEL053 | I/O error encountered on DDSIIN
Explanation | The DD/SIIN job control statement, which specifies the sequential input (SIBA) log data set for ADASEL, is either incorrect or specifies an unavailable data set or device. Another possible cause is that the DD/SIIN data set is not the sequential output file from an ADARES COPY/PLCOPY operation, as required by ADASEL.
Action | Correct the problem and rerun the ADASEL job.

SEL054 | I/O error encountered on DDEXPA
Explanation | The DD/EXPA job control statement, which specifies the print output data set for ADASEL, is either incorrect or specifies an unavailable data set or device.
Action | Correct the problem and rerun the ADASEL job.

SEL055 | Warning: Skipping decompressed record File=fn ISN=isn LRECL for DDEXPAnn should be = nnnnn or more
Explanation | While decompressing a PLOG data set, ADASEL detected a record that was successfully decompressed but that cannot be written to the output file because it does not fit into the DDEXPAnn output buffer and parameter SPANREC was not specified in the OUTPUT statement of the ADASEL job. ADASEL skips the indicated record and continues processing.
Action | The length of the given decompressed PLOG record (including headers) does not exceed the allowable maximum for VB format records, so you can either increase the LRECL value for DDEXPAnn as recommended in the message (NNNNN or more) or specify the SPANREC parameter in the ADASEL OUTPUT statement. Then rerun the ADASEL job.

SEL056 | Warning: Skipping decompressed record File=fn ISN=isn Decompressed length=length Use parameter "SPANREC" of OUTPUT statement for DDEXPAnn
Explanation | While decompressing a PLOG data set, ADASEL detected a record that was successfully decompressed but that cannot be written to the output file because it does not fit into the DDEXPAnn output buffer and parameter SPANREC was not specified in the OUTPUT statement of the ADASEL job. ADASEL skips the indicated record and continues processing.
Action | The length of the given decompressed PLOG record (including headers) exceeds the allowable maximum for VB format records, so this record can be written to the output file only in parts. To do this, specify the SPANREC parameter in the ADASEL OUTPUT statement and rerun the job.

SEL057 | ADADEC DECOMPRESS error - processing aborted
Explanation | While decompressing a file, ADASEL detected a record that it could not decompress.
Action | Record and/or save all output from the job, your input statements and any dump, then contact Software AG technical support for additional instructions.

SEL058 | File is ciphered and cannot be audited
Explanation | ADASEL cannot be run on ciphered files.
Action | Change the file specification to exclude all ciphered files, then rerun the ADASEL job.

SEL059 | Syntax - CHANGES option not permitted with selection of new or deleted records
Explanation | 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.
Action | Remove the CHANGES parameter from the ADASEL syntax.

SEL060 | Change pool is too small - increase NCFLD or NCUPD and rerun
Explanation | 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.
Action | 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.

SEL061 | Syntax - PE/MU index incorrectly specified for CHANGES option
Explanation | 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.
Action | The IF...CHANGES... conditional statement cannot be specified in this case. Redefine the ADASEL statement.

SEL062 | Warning: Skipping decompressed record. ADADEC RC=rc text File=fn ISN=isn Field=fld [PE-index=pe]
Explanation | While decompressing a PLOG data set, ADASEL detected a record that it could not decompress. ADASEL skips the indicated record and continues processing. The reason-code (rc) and the line of explanatory text (text) provide you with more specific information about the error:
Code | Description
--- | ---
4 | A conversion error occurred during decompression. The explanatory text (text) in the message can be one of the following: Truncation not possible Conversion error LOB error Null value with NC option
8 | The record is too long for the decompression buffer in main storage. The explanatory text (text) in the message can be one of the following: Input record too long
Note: The PE-index part of the message text is only printed if the related field is an MU or PE field.
Action | If necessary, record and save all output from the job, your input statements and any dump. Then contact your Software AG technical support representative for assistance.

SEL063 | Utility cannot run with this version
Explanation | The version indicator returned by the accessed database does not match the version of the active utility.
Action | Correct the database referenced in the ADASEL job and rerun the job.

SEL065 | Syntax - COUNT only valid for MU or PE field
Explanation | The COUNT option of the DISPLAY instruction can only specify an MU or PE field.
Action | Correct the COUNT option to specify an MU or PE field or remove the COUNT option and rerun the job.

SEL066 | Syntax - DISPLAY BEFORE/BOTH must be preceded by "IF ... CHANGES"
Explanation | The BEFORE and BOTH options of the DISPLAY instruction can only be specified within IF statements that contain one or more CHANGES criteria.
Action | Correct the DISPLAY instruction syntax and rerun the job.

SEL067 | SELECT FROM FILE not allowed with SELECT FROM USER
Explanation | You cannot specify a SELECT FROM FILE parameter in the same ADASEL job as a SELECT FROM USER parameter.
Action | Correct the ADASEL syntax and rerun the job.

SEL068 | User table overflow -- Increase NU
Explanation | The user table allocation was not large enough.
Action | Increase the ADASEL NU global parameter setting (its default is 20) and rerun the job.

SEL069 | Syntax - Field names not allowed with SELECT FROM USER
Explanation | References to field names were found in a SELECT FROM USER parameter. In a SELECT FROM USER parameter, no field names can be specified in any associated value criteria or in DISPLAY instructions.
Action | Correct the ADASEL syntax and rerun the job.

SEL075 | Error encountered during CHANGE element processing
Explanation | An internal error occurred in CHANGE ELEMENT processing.
Action | Record or save all output from the job, your input statements, and any dumps. Then contact your Software AG support representative for assistance.

SEL076 | Warning DDEBAND defined, ignored
Explanation | The FDTINPUT parameter was not specified for an ADASEL run, but the DDEBAND job statement was defined in the JCL for the run. The job statement is ignored.
Action | No action is required for this informational message unless you intended to pull the FDT from DDEBAND. If this is the case, specify the FDTINPUT parameter and rerun the ADASEL job.

SEL077 | Warning DDSAVE defined, ignored
Explanation | The FDTINPUT parameter was not supplied in an ADASEL run, but the DDSAVE job statement was specified for the run. The job statement is ignored.
Action | No action is required for this informational message unless you intended to pull the FDT from DDSAVE. If this is the case, specify the FDTINPUT parameter and rerun the ADASEL job.

SEL078 | Spanned work pool is too small -- increase LWP and rerun
Explanation | The global LWP ADARUN parameter value is not large enough. LWP specifies the size of the Adabas work pool which is used for assembling PLOG spanned records.
Action | Increase the LWP parameter setting and rerun the ADASEL job.

SEL079 | Warning. Skipping spanned records
Explanation | A spanned record was encountered in the PLOG and parameter SPANREC was not specified in the OUTPUT instruction. This record cannot be processed by the ADASEL utility without the SPANREC parameter and is rejected from further processing.
Action | If spanned record processing is required, specify the SPANREC parameter in the ADASEL OUTPUT instruction and rerun the ADASEL job.

SEL080 | Both DDEBAND and DDSAVE defined. Only one allowed for FDTINPUT
Explanation | Both DDEBAND and DDSAVE job control statements have been defined in the ADASEL job. Only one is allowed, not both.
Action | Correct the ADASEL job and rerun it.

SEL081 | DDEBAND or DDSAVE input must be specified with FDTINPUT option
Explanation | The FDTINPUT parameter was supplied, but neither the DDEBAND or DDSAVE job control statements were included in the ADASEL job.
Action | Supply a valid DDEBAND or DDSAVE job control statement (but not both) and rerun the job.

SEL082 | DDEBAND input not allowed with SELECT FROM USER
Explanation | If SELECT FROM USER is specified for an ADASEL run, DDEBAND is not allowed. Specify DDSAVE instead.
Action | Correct the ADASEL job, specifying DDSAVE and not DDEBAND if SELECT FROM USER is requested. Then rerun the job.

SEL084 | Error during execution of a sequential read on file DDSAVE: rsn-code
Explanation | An error occurred during a sequential read of DDSAVE. The reason code (rsn-code) is given in the message.
Action | Record or save all output from the job, your input statements, and any dumps. Then contact your Software AG support representative for assistance.

SEL085 | I/O error during execution of a sequential read on file DDEBAND: rsn-code
Explanation | An error occurred during a sequential read of DDEBAND. The reason code (rsn-code) is given in the message.
Action | Record or save all output from the job, your input statements, and any dumps. Then contact your Software AG support representative for assistance.

SEL086 | Incorrect FDT found in input data set
Explanation | Either the field definition table (FDT) expected in the first record is missing from the data set or the FDT structure read from the data set does not satisfy the rules.
Action | Verify that the input data set is valid. Supply a correct input data set and rerun the job. If the problem persists, contact your Software AG technical support representative for assistance.

SEL087 | The input data set / file DDEBAND does not have V or VB record format
Explanation | The specified input data set is invalid.
Action | Supply a correct input data set and rerun the ADASEL job.

SEL088 | I/O error during opening/closing of input file DDSAVE: rsn-code
Explanation | An error occurred attempting to open or close the DDSAVE input file. The reason code (rsn-code) for the failure is given in the message. The cause is probably a misspelling of a job control statement name or other JCL error.
Action | Investigate the cause of the error; correct it and rerun the job.

SEL089 | I/O error during opening/closing of input file DDEBAND: rsn-code
Explanation | An error occurred attempting to open or close the DDEBAND input file. The reason code (rsn-code) for the failure is given in the message. The cause is probably a misspelling of a job control statement name or other JCL error.
Action | Investigate the cause of the error; correct it and rerun the job.

SEL090 | Invalid SAVETAPE supplied
Explanation | The data set supplied as the DD/SAVE input data set is not a save tape.
Action | Supply a valid save tape and rerun the job.

SEL091 | Insufficient pool size to keep all external FDTs
Explanation | The pool size for the FDT allocation was insufficient for the number of FDTs found on the save tape. It is possible that the save tape is invalid because the pool size calculation is from the file control block (FCB).
Action | Supply a valid save tape and rerun the job.

SEL092 | Differing FNRs not allowed for DDEBAND FDTINPUT
Explanation | Multiple file numbers are not allowed when DDEBAND is supplied.
Action | Correct the SELECT parameters and rerun the job.

SEL093 | Requested file not found on SAVETAPE Required FNR=fnr
Explanation | The requested file's FDT is not found on the SAVETAPE. The file number of the requested file is given in the message (fnr).
Action | Supply a save tape that contains the FDT needed and rerun the job. If you are unsure of the contents of a save tape, run an ADAREP report from the save tape and review its contents.

SEL094 | SAVETAPE must be from V74 or higher
Explanation | The supplied save tape was not created using Adabas version 7.4 or later.
Action | Supply a save tape created using Adabas version 7.4 or later and rerun the job.

SEL096 | FDT VERSION DOES NOT MATCH WITH PLOG VERSION
Explanation | The PLOG provided is for a different version than the FDT supplied on DDEBAND or DDSAVE.
Action | Supply a correct PLOG or input FDT and rerun the ADASEL job.

SEL097 | Warning secondary segment without primary is rejected
Explanation | A standalone secondary segment (a secondary segment without a primary segment) of a spanned record was encountered in the PLOG. This segment cannot be processed by ADASEL and so is rejected from further processing.
Action | No action is required for this informational message. Probably, Adabas was started with the ADARUN parameter SRLOG=UPD, which instructs the nucleus to write to the PLOG only the modified spanned record segments. If it is necessary to include all spanned PLOG records in ADASEL processing, restart Adabas with the SRLOG parameter set to ALL or PART.

SEL098 | Warning Fieldname fn for ISN=isn could not be fully processed. The entire value is not present on the PLOG. This record is rejected for further processing
Explanation | The spanned record field (fn) and ISN (isn) identified in the message is not available in the PLOG and is specified with CHANGES or value criteria. This record is rejected for further processing.
Action | No action is required for this informational message.

SEL099 | ADASEL terminating due to error
Explanation | This message typically follows another error message which contains more details about the error and indicates that ADASEL terminated abnormally because the NOUSERABEND parameter was specified.
Action | Analyze the previous errors for the run, correct the error condition, and rerun the ADASEL job.

SEL100 | 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 source library (ADAvrs.SRCE). 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.

SEL101 | I/O error during opening/reading of input file TZINFO
Explanation | The time zone specified could not be loaded from the Adabas time zone library (ADAvrs.TZ00).
Action | Make sure that JCL assigns TZINFO to the Adabas time zone library (ADAvrs.TZ00). Amend the JCL and rerun the job.

SEL102 | Syntax - SELECT FROM FILE not allowed with SELECT ETCMD
Explanation | An attempt to specify SELECT ETCMD FROM FILE was made. SELECT ETCMD can only be specified with FROM USER.
Action | Change the syntax to specify FROM USER instead of FROM FILE and try again.

SEL103 | Syntax - DISPLAY ALL not allowed with SELECT ETCMD
Explanation | An attempt was made to specify DISPLAY ALL in the same ADASEL statement as the SELECT ETCMD parameter. When you specify SELECT ETCMD, you restrict the data to only ET data; thus it becomes an illogical condition to specify DISPLAY ALL since the data is not there.
Action | Correct the syntax and try again.

SEL104 | Syntax - ISN not allowed with SELECT ETCMD
Explanation | An attempt was made to specify DISPLAY ISN in the same ADASEL statement as the SELECT ETCMD parameter. When you specify SELECT ETCMD, you restrict the data to only ET data; thus it becomes an illogical condition to specify DISPLAY ISN since the data is not there.
Action | Correct the syntax and try again.

SEL105 | *** ERROR *** Field selection exceeds output buffer size
Explanation | An attempt was made to write specific fields to the EXPAn output data set and the length of the selected fields exceeds the length of the EXPAn output buffer.
Action | Reduce the number of fields selected for output and try again.

SEL106 | Syntax - numeric value too large
Explanation | The specified numeric value for the ADASEL criterion is too large.
Action | Verify the criterion specification for the ADASEL run, correcting values to allowed ranges. Then rerun the ADASEL job.

SEL108 | Timezone file cannot be processed or the transition times are invalid
Explanation | The timezone file cannot be processed.
Action | Make sure that the Adabas time zone library (ADAvrs.TZ00) is readable and the timezone file is unmodified. Contact your Software AG technical support representative for assistance.

SEL109 | PLOG version with time prefix does not match the Adabas version
Explanation | The PLOG cannot be processed. The version indicates that a timestamp should be present and it was not. Check how the PLOG was created, making sure that the PLOG was created at the appropriate Adabas level.
Action | Contact your Software AG technical support representative for assistance, if necessary.

SEL133 | Warning. PLOG has not been merged
Explanation | The PLOG was created by an Adabas cluster nucleus and has not yet been merged using the ADARES PLCOPY procedure.
Action | Merge the PLOGs using the ADARES PLCOPY function before you extract data using ADACDC.