This document covers the following topics:
ABEND (abnormal end) codes are issued primarily by Adabas modules operating with Entire Net-Work. In addition to those listed in the Adabas Messages and Codes documentation, the following ABEND codes specific to the NETSIP/NETSIR initialization programs may also appear:
| Code | Module | Explanation |
|---|---|---|
| 800 | NETSIP/OS | Invalid operating system detected: not OS/390 or z/OS |
| 801 | NETSIP/OS | Parameter error detected |
| 802 | NETSIP/OS | Addressing or residency mode, authorization error, or operating system is not a virtual machine guest |
| 803 | NETSIP/OS | Error detected during program loading or validation |
| 804 | NETSIP/OS | Space allocation failure |
| 806 | NETSIP/OS | NETSIR initialization failed |
Entire Net-Work itself issues only the ABEND code 253 to indicate that an abnormal termination occurred. The specific termination information is given in the messages written to the print dataset.
Adabas response codes that refer to problems with the interregion communication in one way or another may occur when running Entire Net-Work. Refer to the Adabas Messages and Codes documentation for information about these codes.
In Entire Net-Work environments, the cause for these response codes is not always as apparent as in single systems. This is due to the fact that all calls are passed through interregion communications in two places: first they are passed from the user's task to Entire Net-Work; then, on the server's node, they are passed from Entire Net-Work to the server. In both instances, the same types of errors may occur. Therefore it is sometimes difficult if not impossible to determine the node on which the problem was encountered.
To aid in diagnosing such situations, Entire Net-Work provides the node ID (target ID) of the Entire Net-Work node where the problem was encountered for all problems related to these response codes. The information is returned in the additions 2 field of the Adabas control block. Note that this field is not modified by Entire Net-Work under any other circumstances. In some cases, where the problem prevents the call from reaching Entire Net-Work on the user's node, the information obviously cannot be provided by Entire Net-Work.
In addition, a group of Adabas codes ranging from 220 through 229 is reserved for use by Entire Net-Work (222, 223, 225-228 are not currently used):
| Response 220 | |
| Explanation |
Buffer shortage: the request was rejected by Entire Net-Work due to a shortage of short term buffers. The additions 2 field in the Adabas control block contains the node ID of the node in error in the leftmost 2 bytes. |
| Action |
Increase the size of the short term buffer allocated on the
|
| Response 221 | |
| Explanation |
The LU size of the remote partner is smaller than the size required for the Adabas request. |
| Action |
Either increase the size specified for the |
| Response 224 | |
| Explanation |
Reply timeout: the request waited for a reply for a longer time period
than specified by the |
| Action |
This message is for information only. |
| Response 229 | |
| Explanation |
Translation error: the Entire Net-Work converter detected an inconsistency and/or error in the application format buffer or search buffer and is unable to correctly translate the user's data. |
| Action |
This message is for information only. |
