Errors Common to All Utilities

#### Search Results

Search

# Errors Common to All Utilities

### Overview of Messages

`ERROR-001 | ERROR-002 | ERROR-003 | ERROR-004 | ERROR-005 | ERROR-006 | ERROR-007 | ERROR-008 | ERROR-009 | ERROR-010 | ERROR-011 | ERROR-012 | ERROR-013 | ERROR-014 | ERROR-015 | ERROR-016 | ERROR-017 | ERROR-018 | ERROR-019 | ERROR-020 | ERROR-021 | ERROR-022 | ERROR-023 | ERROR-024 | ERROR-025 | ERROR-026 | ERROR-027 | ERROR-028 | ERROR-029 | ERROR-030 | ERROR-031 | ERROR-032 | ERROR-033 | ERROR-034 | ERROR-035 | ERROR-036 | ERROR-037 | ERROR-038 | ERROR-039 | ERROR-040 | ERROR-041 | ERROR-042 | ERROR-043 | ERROR-044 | ERROR-045 | ERROR-046 | ERROR-047 | ERROR-048 | ERROR-049 | ERROR-051 | ERROR-052 | ERROR-053 | ERROR-054 | ERROR-055 | ERROR-057 | ERROR-058 | ERROR-059 | ERROR-060 | ERROR-062 | ERROR-064 | ERROR-065 | ERROR-066 | ERROR-067 | ERROR-068 | ERROR-069 | ERROR-070 | ERROR-071 | ERROR-072 | ERROR-073 | ERROR-074 | ERROR-075 | ERROR-076 | ERROR-077 | ERROR-078 | ERROR-079 | ERROR-080 | ERROR-081 | ERROR-084 | ERROR-085 | ERROR-086 | ERROR-087 | ERROR-088 | ERROR-089 | ERROR-090 | ERROR-091 | ERROR-092 | ERROR-093 | ERROR-094 | ERROR-098 | ERROR-099 | ERROR-101 | ERROR-102 | ERROR-103 | ERROR-104 | ERROR-105 | ERROR-106 | ERROR-107 | ERROR-108 | ERROR-109 | ERROR-110 | ERROR-111 | ERROR-112 | ERROR-113 | ERROR-114 | ERROR-115 | ERROR-116 | ERROR-117 | ERROR-118 | ERROR-120 | ERROR-242 | ERROR-243 | ERROR-245 | ERROR-246 | ERROR-247 | ERROR-248 | ERROR-249 | ERROR-250 | ERROR-251 | ERROR-252 | ERROR-253 | ERROR-254 | ERROR-255 | ERROR-257 | ERROR-258 | ERROR-259 | ERROR-260`

ERROR-001 | Error occurred during opening input file DDKARTE : reason
Explanation | The cause is probably a misspelled keyword.
Action | Check the JCL; correct the error and rerun the job.

ERROR-002 | I/O error occurred during read on file DDKARTE : reason
Explanation | The cause is probably a misspelled keyword.
Action | Check the JCL; correct the error and rerun the job.

ERROR-003 | Parameter error, invalid utility name
Explanation | The cause is probably a misspelled keyword.
Action | Check the parameter input; correct the error and rerun the job.

ERROR-004 | Parameter error, missing separator
Action | Correct the parameter error or supply the missing separator. Rerun the job.

ERROR-005 | Parameter error, invalid syntax
Action | Supply the correct parameter value and rerun the job.

ERROR-006 | Parameter error, keyword not unique
Action | Check the parameter input; supply the correct keyword in full length and rerun the job.

ERROR-007 | Parameter error, unknown parameter
Explanation | The cause is probably a misspelled keyword.
Action | Check the parameter input; correct the error and rerun the job.

ERROR-008 | Parameter error, unknown function
Explanation | The cause is probably a misspelled keyword.
Action | Check the parameter input; correct the error and rerun the job.

ERROR-009 | Parameter error, too many values in a list
Action | Check the parameter input. Supply no more than the maximum number of parameter values permitted, and rerun the job.

ERROR-010 | Invalid or missing level number
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-011 | Invalid or missing field length
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-012 | Missing `=' (equal sign)
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-013 | Invalid or missing field option
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-014 | Missing `(' (left parenthesis)
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-015 | Missing `)' (right parenthesis)
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-016 | Invalid or missing start position
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-017 | Invalid or missing end position
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-018 | More than one parent for sub-field/descriptor
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-019 | More than 20 parents for super-field/descriptor
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-020 | Only one parent for super-field/descriptor
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-021 | Syntax error, invalid character found
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-022 | Invalid or missing hyperdescriptor exit number or collating exit number
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-023 | No or more than 20 parents for a hyperdescriptor
Action | See the ADACMP discussion in the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-024 | Invalid field name
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-025 | Reserved field name used
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-026 | Invalid field format specification
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-027 | Invalid or conflicting field options used
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-028 | Invalid MU/PE repeat factor
Action | See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

ERROR-029 | Multiple function keywords detected
Explanation | This utility performs only one function per execution.
Action | Check the parameter input; correct the error and rerun the job.

ERROR-030 | Error occurred during execution of open ASSO : reason
Explanation | The cause is probably incorrect JCL (DDASSOR1, ..., DDASSOR5) or an inconsistent database.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-031 | Error occurred during execution of read ASSO : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-032 | Error occurred during execution of write ASSO : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job. Note: If this error occurs in a BS2000 environment when running ADAFRM, please check that the size of the container is track-rounded. For more information, read Splitting Data Sets Across Volumes under BS2000 Device Types and Block Sizes.

ERROR-033 | Error occurred during execution of close ASSO : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-034 | Error occurred during execution of open DATA : reason
Explanation | The cause is probably incorrect JCL (DDDATAR1, ..., DDDATAR5) or an inconsistent database.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-035 | Error occurred during execution of read DATA : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-036 | Error occurred during execution of write DATA : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-037 | Error occurred during execution of close DATA : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-038 | Error occurred during execution of open WORK : reason
Explanation | The cause is probably incorrect JCL (DDWORKR1) or an inconsistent database.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-039 | Error occurred during execution of read WORK : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-040 | Error occurred during execution of write WORK : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-041 | Error occurred during execution of close WORK : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-042 | Error occurred during execution of open TEMP : reason
Explanation | The cause is probably incorrect job control (DD/TEMPR1).
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-043 | Error occurred during execution of read TEMP : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-044 | Error occurred during execution of write TEMP : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-045 | Error occurred during execution of close TEMP : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-046 | Error occurred during execution of open SORT : reason
Explanation | The cause is probably incorrect job control (DD/SORTR1 or DD/SORTR2).
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-047 | Error occurred during execution of read SORT : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-048 | Error occurred during execution of write SORT : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-049 | Error occurred during execution of close SORT : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-051 | Error occurred during execution of open dataset/file : reason
Explanation | The cause is probably incorrect JCL.
Action | The correct JCL must be supplied to the function. Please also ensure that the DEVICE parameter is correct. If this is for a PLCOPY job and the PLOGs to be copied are from a cluster database, the NOPPT parameter should be specified. If no JCL is supplied or the open fails, the following will be displayed: "The Associator data set(s) could not be opened nn - return code explanation. " Processing continues. If you are using mixed devices for different data sets of the database when running the ADACNV utility, you might also specify the PLOGDEV parameter in the ADACNV run.

ERROR-052 | Error occurred during execution of read dataset/file : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-053 | Error occurred during execution of write dataset/file : reason RABN : nnnn (xxxxxxxx)
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-054 | Error occurred during execution of close dataset/file : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-055 | Encoding key value exceeds maximum of 4095
Explanation | Valid encoding keys are in the range 1-4095.
Action | See the Adabas Utilities documentation for a list of valid encoding keys.

ERROR-057 | Utility function not permitted by Adabas SAF Security
Explanation | Adabas is running with the Adabas SAF Security, which has been configured to provide protection at the utility function level (SAFCFG parameter UTI=2) or the utility function/file level (UTI=3). Adabas SAF Security has not permitted the execution of the specified utility function (if UTI=3, on the specified files) by the current user.
Action | Determine whether the current user ought to be able to execute the specified function (on the specified files) or whether this function should be run by another user (or not at all).

ERROR-058 | Recover log not available
Explanation | The Adabas Recovery Aid is active, but an error occurred when the utility attempted to initialize RLOG data set processing.
Action | ADARAC returns reason code rr: reason text . See also the accompanying ADARxx message.

ERROR-059 | Error during recovery logging
Explanation | The utility was not able to record its operation in the recovery log. The utility continues and will terminate with return code 4.
Action | ADARAC returns reason code rr: reason text . See also the accompanying ADARxx message.

ERROR-060 | blocks-Extent space allocation failed for file file-number(s)
Explanation | An attempt to allocate an AC extent of size blocks for the file or files specified failed. Probable causes of the failure include not enough free space available. conflicting XXRABN parameter. enough free space available, but not on devices that can satisfy the MAXRECL value for this file. only one AC extent permitted. If ISNSIZE=3, more than 16,777,215 (X'FF FF FF) ISNs; if ISNSIZE=4, more than 4,294,967,294 (X'FF FF FF FE) ISNs. more than 5 extents.
Action | Correct the error and rerun the job.

ERROR-062 | For file filename the sum of numbers of DATA extents, AC extents, UI extents, and NI extents is too big or DATA extent or AC extent is zero. Check ASSO RABN rabn
Explanation | A database problem exists. The sum of Data Storage, address converter (AC), and inverted list (UI and NI) extents is too large or the Data Storage or address converter extents are zero.
Action | Contact you Software AG technical support representative for assistance.

ERROR-064 | Error writing DSST : response-code
Explanation | The nucleus returned response code "nn" while writing the DSST to the database. The file(s) being accessed remain(s) in an inaccessible state.
Action | Investigate the cause of the problem; correct the error and rerun the job.

ERROR-065 | Database ID mismatch: the ADARUN DBID is dbid-a but the GCB contains DBID dbid-b
Explanation | One of the following occurred: the wrong database was accessed; or an input parameter specified an incorrect database ID.
Action | Correct the error and rerun the job.

ERROR-066 | File file-number is password protected
Explanation | A password-protected file "file-number" cannot be processed without the nucleus. The nucleus is required to access the Adabas security file and to validate the supplied password.
Action | Start the Adabas nucleus and rerun the job.

ERROR-067 | Invalid or missing password for file file-number
Explanation | The requested file "file-number" is password protected.
Action | Supply the correct password and rerun the job.

ERROR-068 | Utility communication block overflow
Explanation | Too many utilities are running in parallel.
Action | Inform your database administrator.

ERROR-069 | Checkpoint block overflow
Explanation | The Associator block containing data for checkpoints written offline is filled.
Action | Start the nucleus to pick up information currently stored in the offline checkpoint area; then rerun the job.

ERROR-070 | Error writing checkpoint: response-code
Explanation | The nucleus returned the specified response code while writing a checkpoint.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-071 | Invalid value for parameter parm. Only values ''YES'' or ''NO'' are allowed.
Explanation | An invalid parameter value was specified for the parameter named in the message (parm). The only valid values are "YES" or "NO".
Action | Supply the correct parameter value and rerun the job.

ERROR-072 | Unexpected nucleus response nucleus-response-code subcode- description
Explanation | An unexpected nucleus response occurred. The Adabas response code, subcode, and a description of the problem are provided in the message. For more information about the response code, refer to Adabas Response Codes .
Action | Note and keep any related error information or output. Inform your DBA. If necessary, contact your Software AG technical support representative.

ERROR-073 | Record too long for output data set
Explanation | An attempt was made to write a record to the sequential output data set. The length of the requested record exceeded the maximum record length permitted by the I/O system.
Action | Inform your database administrator.

ERROR-074 | file-number is an invalid file number
Explanation | The supplied file number: is zero; is greater than the MAXFILES parameter in effect for the database; has been duplicated in the file list specified; or represents a system file and is greater than 5000.
Action | Supply a correct file number and rerun the job.

ERROR-075 | The parameter parameter is mutually exclusive to one or more other parameters supplied in the input
Explanation | The setting of the specified parameter conflicts with at least one other parameter setting in the related utility job. See the description of the utility syntax in the Adabas Utilities documentation for more information.
Action | Change or remove one of the mutually exclusive parameter settings, and rerun the job.

ERROR-076 | Mandatory parameter parameter missing
Action | Add this parameter and rerun the job.

ERROR-077 | I/O error during execution of a sequential read on file ddname : reason
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-078 | Error occurred during opening of file ddname for output: reason
Explanation | The cause is probably a misspelling of the DDNAME, incorrect JCL, etc.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-079 | Error occurred during closing of output file ddname : reason
Explanation | The cause is probably a misspelling of the DDNAME, incorrect JCL, etc.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-080 | Error occurred during execution of write command to file ddname : reason
Explanation | The cause is probably a misspelling of the DD/NAME, incorrect JCL, an incorrect record or block size specification, or some similar problem.
Action | Investigate the cause of the error; correct it and rerun the job.

ERROR-081 | Error occurred during opening/closing of input file ddname : reason
Explanation | An error occurred attempting to open or close the input file identified in the message (ddname). The reason code (reason) 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.

ERROR-084 | GETMAIN error - not enough virtual memory requested length = count (hex-count) bytes memory gotten = count (hex-count) bytes
Action | Rerun the job in a larger partition/region.

ERROR-085 | GETMAIN Error - not enough virtual memory Reported by ADAIOR function fxname
Explanation | A GETMAIN error occurred. There is not enough virtual memory to process the ADAIOR function referenced in the message (fxname).
Action | Rerun the job in a larger partition or region.

ERROR-086 | Invalid { ASSO | DATA } RABN nnnn : reason
Explanation | This RABN is not defined in the database.
Action | Check the input parameters; correct the error and rerun the job.

ERROR-087 | device is an unknown disk device type
Explanation | An invalid or unknown device type was found during processing.
Action | Check the input parameters; correct the error and rerun the job.

ERROR-088 | ADALNK and/or ADANUC not present
Explanation | The Adabas installation procedure was not properly executed.
Action | Inform your database administrator.

ERROR-089 | Utility not permitted to run
Explanation | Another utility has exclusive database control. The table displayed below the message on the terminal screen shows the current contents of the utility communications block. One of the jobs displayed has exclusive database control.
Action | Wait until that job has ended and retry this function.

ERROR-090 | Utility not permitted to run; file number file-number is locked by another utility
Explanation | The table displayed below the message on the terminal screen shows the current contents of the utility communications block. One of the jobs displayed has exclusive file control.
Action | Wait until that job has ended, and then retry this function.

ERROR-091 | Utility not permitted to run
Explanation | Concurrent jobs are not allowed to run against the database. In this case, the nucleus or another utility is active; or the nucleus was started with ADARUN READONLY=YES.
Action | Determine which utility/nucleus is already active. Wait until that utility/nucleus has ended and retry this function. If the nucleus was started with READONLY=YES, shut it down and restart with READONLY=NO.

ERROR-092 | Utility not permitted to run
Explanation | The Adabas nucleus returned response "nn -xxx nucleus response -xxx". The nucleus cannot allow access to the requested file.
Action | Analyze the nucleus response code. Correct the error and rerun the job.

ERROR-093 | Utility not permitted to run
Explanation | Pending autorestart detected.
Action | Restart the nucleus to perform the autorestart. Perform a shutdown after successful nucleus start if required. Rerun this job.

ERROR-094 | Utility not permitted to run
Explanation | The version of the accessed database conflicts with the version of the active utility. Either the version indicator in the GCBs or the version indicator returned by the Adabas nucleus is not correct. The version indicator found is "version" (the text of the messages supplies the actual version indicator value).
Action | Correct the database or load library specification and rerun the job.

ERROR-098 | File file-number cannot be processed
Explanation | The file comes from a database with a higher version number, and uses features not supported in the current nucleus version.
Action | It is not possible to process this file using the current version of the Adabas nucleus or utilities.

ERROR-099 | Internal error at xxxxxx+yyyyyy
Explanation | Register contents at time of error:
R0-R3 | xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
R4-R7 | xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
R8-R11 | xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
R12-R15 | xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
Action | Inform your database administrator.

ERROR-101 | Value for unique descriptor xx in file yy already present
Explanation | Input data is invalid; the specified file yy cannot be processed. ISN=nnnn DE-VALUE: llvvvvvvvv The descriptor value (DE-VALUE) comprises the length of the descriptor value (ll) followed by the actual value (vvvvvvvv).
Action | Rerun the utility with unique input data.

ERROR-102 | An attempt was made to create a 16th index level for file xxx
Explanation | No more than 15 levels are permitted.
Action | Rerun this function with a smaller value for ASSOPFAC, the Associator padding factor.

ERROR-103 | File number file-number is not accessible
Explanation | One of the following occurred: A previous function to LOAD, REFRESH, REORDER, or RESTORE the file was interrupted. It is inconsistent. A RESTONL FMOVE function or RESTONL FILE function with parameter ALLOCATION=NOFORCE was interrupted; continuing the function with RESTPLOG is not possible.
Action | Delete the file or overwrite it using ADAORD STORE or ADASAV RESTORE/RESTONL.

ERROR-104 | File number file-number is already loaded
Explanation | The file being accessed is already present in the database.
Action | Look at the database report. Delete the file or choose another file number, then rerun the job.

ERROR-105 | File number file-number is not loaded
Explanation | The file being accessed is not present in the database.
Action | Check the file number; correct it and rerun the job.

ERROR-106 | Compressed record too long
Explanation | ISN of record = nnnn Length of record = nnn bytes Maximum record length = nnn bytes The characteristics of the data storage device do not allow such a record to be stored.

ERROR-107 | The value of the `SORTSIZE' parameter and the size of the SORT dataset do not match.
Explanation | The data set is smaller than specified.
Action | Supply the correct size and rerun the job.

ERROR-108 | The value of the `TEMPSIZE' parameter and the size of the TEMP dataset do not match.
Explanation | The data set is smaller than specified.
Action | Supply the correct size and rerun the job.

ERROR-109 | Workpool (LWP) too small
Explanation | At least nnnnK of space is required. A larger value will increase performance.
Action | Increase the ADARUN LWP parameter value and rerun the job.

ERROR-110 | SORT dataset too small
Explanation | Sorting may require either a larger SORTRn/DDSORTRn data set size, or two Sort data sets with a SORTSIZE equal to the combined size of both data sets.
Action | Supply a larger sort data set and increase the appropriate SORTSIZE= parameter. Decreasing the LWP parameter specified with the job might also help. The rules for the sort data set space calculation are described in the Adabas Utilities documentation. Rerun the job using the RESTART parameter.

ERROR-111 | Invalid value for the parameters MINISN and/or MAXISN
Explanation | The MINISN and MAXISN parameter values must satisfy the following expression: If the ISNSIZE is 3: 0 < MINISN <= MAXISN < (MINISN + 16,777,215) If the ISNSIZE is 4: 0 < MINISN <= MAXISN < (MINISN + 4,294,967,294)
Action | Supply the correct parameter value and rerun the job.

ERROR-112 | Function not permitted
Explanation | An attempt was made to access an Adabas system file. This is not permitted.
Action | Correct the error and rerun the job.

ERROR-113 | Invalid value for the parameter parameter
Explanation | An invalid value was specified for the parameter named in the message (parameter). The only values allowed are YES or NO.
Action | Supply the correct parameter value and rerun the job.

ERROR-114 | Invalid value for the parameter ASSOPFAC or DATAPFAC
Explanation | The value for a padding factor must be in the range 1 to 90%.
Action | Supply the correct parameter value and rerun the job.

ERROR-115 | Invalid value for the parameter MAXRECL
Explanation | The value for MAXRECL must be all of the following: greater than 4; less than or equal to the Work block size minus 94; less than or equal to the Data Storage block size minus 4; equal to the MAXRECL of the anchor file (for components of expanded files).
Action | Supply the correct parameter value and rerun the job.

ERROR-116 | Invalid value for the parameter MAXFILES
Explanation | The value for the parameter MAXFILES must meet the following requirements: the parameter value must be in the range 3 to "nnnn" where "nnnn" is the Associator block size minus 1. the first (MAXFILES*5)+30 blocks must fit into the first Associator extent.
Action | Supply the correct parameter value and rerun the job.

ERROR-117 | Parallel usage of dataset-name dataset
Explanation | data-set-name RABN rabn-number (value) was overwritten by another utility.
Action | Rerun the job, and avoid parallel usage of the "data-set-name" data set.

ERROR-118 | The maximum record length of the ddname dataset is not large enough to accommodate the record length of the input file.
Explanation | The maximum record length (MAXRECL) of the file identified in the message (ddname) is not long enough for the data intended to be written to it.
Action | Correct the MAXRECL setting of the data set so it is equal to or larger than the maximum record length of the records being input. Then resubmit the job.

ERROR-120 | Invalid value for parameter `ISNSIZE'
Explanation | Either 3 or 4 may be specified for this parameter.
Action | Check the parameter input; correct any errors, then rerun the job.

ERROR-242 | Invalid FILE number specified for auditing
Explanation | The ADADBS AUDITING function is only valid for files participating in auditing (are included in an ADAANP FILE group).
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-243 | The specified FILE was already active|inactive
Explanation | The database detected the file identified in the message was already active or inactive.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-245 | AUDITSERVER function only allowed for use with the Audit Server
Explanation | The ADADBS AUDITSERVER function is only valid for an Audit Server.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-246 | The specified destination destination was not found
Explanation | The destination identified in the message is not defined to the Audit Server.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-247 | The specified subscription subscription was not found
Explanation | The subscription identified in the message is not defined to the Audit Server.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-248 | The specified destination destination was already active|inactive
Explanation | The Audit Server detected the destination identified in the message was already active or inactive.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-249 | The specified subscription subscription was already active|inactive
Explanation | The Audit Server detected the subscription identified in the message was already active or inactive.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-250 | Missing parameter: DESTINATION required
Explanation | ADADBS detected that the required parameter `DESTINATION` was missing.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-251 | Missing parameter: DESTINATION or SUBSCRIPTION required
Explanation | ADADBS detected that the required parameter `DESTINATION` or `SUBSCRIPTION` was missing.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-252 | SUBSCRIPTION parameter not allowed for OPEN or CLOSE: only DESTINATION
Explanation | ADADBS detected invalid parameter SUBSCRIPTION with OPEN or CLOSE.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-253 | The specified subscription subscription was not activated|deactivated
Explanation | The Audit Server detected an unexpected response code from an attempt to activate or deactivate the subscription identified in the message.
Action | Investigate the cause of the error. Correct it and rerun the job. If the cause of the error cannot be determined, contact your Software AG technical support representative.

ERROR-254 | Auditing not active for Adabas
Explanation | The database is not an auditing database (`ADARUN AUDITING=YES`).
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-255 | NUCID specified for a non-cluster Adabas DBID
Explanation | The `NUCID=` parameter was specified for a non-cluster Adabas database.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-257 | {CLOSE | OPEN} failed for specified destination destination
Explanation | ADADBS detected that the Audit Server could not CLOSE or OPEN the destination identified in the message.
Action | Investigate the cause of the error. The Audit Server job log will provide more details on why the request failed.

ERROR-258 | The specified destination destination cannot be activated.Data still exists on the SLOG system file for this inactive destination.
Explanation | An attempt was made to activate the destination identified in the message while items for the destination still exist on the SLOG system file from the last time it was active.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-259 | The specified destination destination was already open|closed
Explanation | The Audit Server detected the destination identified in the message was already open or closed for all tasks.
Action | Investigate the cause of the error. Correct it and rerun the job.

ERROR-260 | The specified destination destination was not activated|deactivated
Explanation | The Audit Server detected an unexpected response code from an attempt to activate or deactivate the destination identified in the message.
Action | Investigate the cause of the error. Correct it and rerun the job. If the cause of the error cannot be determined, contact your Software AG technical support representative.