The Adabas utilities issue return/condition codes, and may also display error messages. This document lists, alphabetically by utility, the utility error messages and describes the utility nonzero return codes.
Utility messages are displayed following a title line showing the utility name. The message line itself is displayed, followed by the same "explanation" and/or "action" information shown in this chapter.
Variable information such as jobname, data set name, return code, abend code, or nucleus response code may occur in the message line or in the text following the actual message. These variables are represented in lowercase as either "xxx...xxx" or as "reason", "nucleus-response", "job-name", "ret-code", and so on. In the actual message these notations are replaced with the actual values. Generally, variables within parentheses ( ) are hexadecimal and those without parentheses are decimal.
When a message includes a nucleus response or abend code, the specific code description identifies the cause. See the description of nucleus response codes and abend codes.
Error messages are described for the following utilities:
When an Adabas utility returns control to the operating system and no abend has occurred, the utility writes a return codes in the rightmost positions of general register 15:
Code | The utility operation ... |
---|---|
0 | was successful. |
4 | was successful but encountered a warning condition. |
8 | was not successful. |
Note:
Utilities that terminate with return code 4 write
"...terminated with warning" as the last message. This indicates that, although
the utility function completed successfully, circumstances may have rendered
the result of the function different from that which was expected. The job
protocol contains one or more related warning or error messages.
Return codes are supported by operating system as described in the following table:
Operating System | Return Code Support |
---|---|
z/OS | See the job control language reference manuals for job step condition code information. |
z/VSE | Return codes are supported. |
BS2000 | Return codes are supported using job variables. For more information, see the Adabas Installation documentation, section How to Manage Job Variables in the Adabas Environment. |
Depending on the operating system and the utility, the return code can be tested to determine the utility job status:
A zero return code always indicates successful completion of the utility.
The meanings of return codes 4 or 8 depend on the utility in operation at the time.
These unsuccessful return code (RC) meanings are described here in alphabetical order by Adabas utility.
Return Code 0 | |
Explanation |
ADACHK was successful. |
Return Code 4 | |
Explanation |
ADACHK was successful but encountered a warning condition. With the ADACHK utility, a return code of 4 indicates that either the number of unreachable index blocks is greater than zero or any CHKnnnW (warning) message was received. |
Return Code 8 | |
Explanation |
ADACHK encountered an error condition but then continued. With the ADACHK utility, a return code of 8 indicates that a database inconsistency was encountered. |
Return Code 20 | |
Explanation |
The function could not be completed. The operation encountered an error condition but did not terminate abnormally because NOUSERABEND was specified. |
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 8 | |
Explanation |
The utility detected inconsistencies between the files in a LOB group (a base file and its associated LOB file). |
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 8 | |
Explanation |
One of the following occurred:
|
Return Code 4 | |
Explanation |
NEWWORK: Attempt to write RLOG information or close RLOG data set failed. |
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 8 | |
Explanation |
One of the following occurred:
|
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 4 | |
Explanation |
ADARAI RECOVER cannot create the job control statements needed for the sequential file used during utility execution. The message "unknown file element" is returned and the RECOVER function completes with return code 4. The generated job control must then be edited. See message ADAR78. |
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 8 | |
Explanation |
One of the following occurred:
|
Return Code 16 | |
Explanation |
An error occurred after the PLCOPY/CLCOPY function successfully closed the DD/SIAUS1 or DD/SIAUS2 data set. The error message is printed in DD/DRUCK. |
Return Code 4 | |
Explanation |
One of the following occurred:
|
Return Code 16 | |
Explanation |
(Adabas Delta Save Facility Facility) An error occurred after a full or delta save operation completed successfully. |
Return Code 4 | |
Explanation |
No records were found matching the selection criterion. |
Return Code 4 | |
Explanation |
One of the following has occurred:
|
Return Code 8 | |
Explanation |
The nucleus returned a non-zero response code. Depending on the ERRLIM parameter of ADAULD UNLOAD, the function may continue. Unloaded data can be used, but records may be missing depending on the particular response code returned. |
Return Code 4 | |
Explanation |
No autorestart information available on Work Part 1 |
Return Code 8 | |
Explanation |
Autorestart will not complete successfully . |
Return Code 20 | |
Explanation |
This return code is returned instead of an abend when the NOUSERABEND parameter is specified. |