Errors Common to All Utilities

The cause is probably a misspelled keyword.

Check the JCL; correct the error and rerun the job.

The cause is probably a misspelled keyword.

Check the JCL; correct the error and rerun the job.

The cause is probably a misspelled keyword.

Check the parameter input; correct the error and rerun the job.

Correct the parameter error or supply the missing separator. Rerun the job.

Supply the correct parameter value and rerun the job.

Check the parameter input; supply the correct keyword in full length and rerun the job.

The cause is probably a misspelled keyword.

Check the parameter input; correct the error and rerun the job.

The cause is probably a misspelled keyword.

Check the parameter input; correct the error and rerun the job.

Check the parameter input. Supply no more than the maximum number of parameter values permitted, and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the ADACMP discussion in the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

See the Adabas Utilities documentation for more information about field definition syntax. Correct the error and rerun the job.

This utility performs only one function per execution.

Check the parameter input; correct the error and rerun the job.

The cause is probably incorrect JCL (DDASSOR1, ..., DDASSOR5) or an inconsistent database.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

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.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably incorrect JCL (DDDATAR1, ..., DDDATAR5) or an inconsistent database.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably incorrect JCL (DDWORKR1) or an inconsistent database.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably incorrect job control (DD/TEMPR1).

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably incorrect job control (DD/SORTR1 or DD/SORTR2).

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably incorrect JCL.

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.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

Valid encoding keys are in the range 1-4095.

See the Adabas Utilities documentation for a list of valid encoding keys.

The Adabas Recovery Aid is active, but an error occurred when the utility attempted to initialize RLOG data set processing.

ADARAC returns reason code rr: reason text . See also the accompanying ADARxx message.

The utility was not able to record its operation in the recovery log. The utility continues and will terminate with return code 4.

ADARAC returns reason code rr: reason text . See also the accompanying ADARxx message.

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.

Correct the error and rerun the job.

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.

Contact you Software AG technical support representative for assistance.

The nucleus returned response code "nn" while writing the DSST to the database. The file(s) being accessed remain(s) in an inaccessible state.

Investigate the cause of the problem; correct the error and rerun the job.

One of the following occurred:

• the wrong database was accessed; or

• an input parameter specified an incorrect database ID.

Correct the error and rerun the job.

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.

Start the Adabas nucleus and rerun the job.

The requested file "file-number" is password protected.

Supply the correct password and rerun the job.

Too many utilities are running in parallel.

Inform your database administrator.

The Associator block containing data for checkpoints written offline is filled.

Start the nucleus to pick up information currently stored in the offline checkpoint area; then rerun the job.

The nucleus returned the specified response code while writing a checkpoint.

Investigate the cause of the error; correct it and rerun the job.

An invalid parameter value was specified for the parameter named in the message (parm). The only valid values are "YES" or "NO".

Supply the correct parameter value and rerun the job.

An unexpected nucleus response occurred. The Adabas response code, subcode, and a description of the problem are provided in the message.

Note and keep any related error information or output. Inform your DBA. If necessary, contact your Software AG technical support representative.

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.

Inform your database administrator.

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.

Supply a correct file number and rerun the job.

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.

Change or remove one of the mutually exclusive parameter settings, and rerun the job.

Add this parameter and rerun the job.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably a misspelling of the DDNAME, incorrect JCL, etc.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably a misspelling of the DDNAME, incorrect JCL, etc.

Investigate the cause of the error; correct it and rerun the job.

The cause is probably a misspelling of the DD/NAME, incorrect JCL, etc.

Investigate the cause of the error; correct it and rerun the job.

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.

Investigate the cause of the error; correct it and rerun the job.

Rerun the job in a larger partition/region.

This RABN is not defined in the database.

Check the input parameters; correct the error and rerun the job.

An invalid or unknown device type was found during processing.

Check the input parameters; correct the error and rerun the job.

The Adabas installation procedure was not properly executed.

Inform your database administrator.

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.

Wait until that job has ended and retry this function.

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.

Wait until that job has ended, and then retry this function.

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.

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.

The Adabas nucleus returned response "nn -xxx nucleus response -xxx". The nucleus cannot allow access to the requested file.

Analyze the nucleus response code. Correct the error and rerun the job.

Pending autorestart detected.

Restart the nucleus to perform the autorestart. Perform a shutdown after successful nucleus start if required. Rerun this job.

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).

Correct the database or load library specification and rerun the job.

The file comes from a database with a higher version number, and uses features not supported in the current nucleus version.

It is not possible to process this file using the current version of the Adabas nucleus or utilities.

Register contents at time of error:

Inform your database administrator.

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).

Rerun the utility with unique input data.

No more than 15 levels are permitted.

Rerun this function with a smaller value for ASSOPFAC, the Associator padding factor.

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.

Delete the file or overwrite it using ADAORD STORE or ADASAV RESTORE/RESTONL.

The file being accessed is already present in the database.

Look at the database report. Delete the file or choose another file number, then rerun the job.

The file being accessed is not present in the database.

Check the file number; correct it and rerun the job.

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.

The data set is smaller than specified.

Supply the correct size and rerun the job.

The data set is smaller than specified.

Supply the correct size and rerun the job.

At least nnnnK of space is required. A larger value will increase performance.

Increase the ADARUN LWP parameter value and rerun the job.

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.

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.

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)

Supply the correct parameter value and rerun the job.

An attempt was made to access an Adabas system file. This is not permitted.

Correct the error and rerun the job.

An invalid value was specified for the parameter named in the message (parameter). The only values allowed are YES or NO.

Supply the correct parameter value and rerun the job.

The value for a padding factor must be in the range 1 to 90%.

Supply the correct parameter value and rerun the job.

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).

Supply the correct parameter value and rerun the job.

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.

Supply the correct parameter value and rerun the job.

data-set-name RABN rabn-number (value) was overwritten by another utility.

Rerun the job, and avoid parallel usage of the "data-set-name" data set.

Either 3 or 4 may be specified for this parameter.

Check the parameter input; correct any errors, then rerun the job.