| Text | The specified password was not found. DB/FNR .../.... |
| Actn. | Check program and correct error, or contact your database
administrator. |
| Text | Incorrect Adabas password for secured file. DB/FNR .../.... |
| Expl. | The specified Adabas password does not allow you to access/update the desired Adabas-secured file. Adabas backs out any open transaction. |
| Actn. | Check program and correct error, or contact your database
administrator. |
| Text | User not authorized to access secured file. DB/FNR .../.... |
| Expl. | The file to be accessed is protected by Adabas Security. To delete a record from that file, you must provide the correct Adabas password. Adabas backs out any open transaction. |
| Actn. | Check program and correct error, or contact your database
administrator. |
| Text | The password pool has overflowed. DB/FNR .../.... |
| Actn. | Contact your database administrator. |
| Text | Logon phase 1 completed for Adabas ESI interface. DB/FNR .../.... |
| Expl. | The Adabas ESI interface completed phase 1 of logon and requested phase 2. |
| Actn. | Send a phase-2 logon request to ADAESI. |
| Text | Execute a phase 1 logon. DB/FNR .../.... |
| Expl. | As an ESI remote user, you should execute a phase 1 logon. The logon ID and your password will be sent to ADAESI. |
| Actn. | Platform does not have the correct Adabas link routine installed. Response code is intercepted by workstation Adabas link routine and phase 1 logon is performed. |
| Text | Adabas External-Security-Interface detects an expired password. |
| Expl. | Adabas ESI (External Security Interface) detects an expired
password on the server. |
| Actn. | Refer to "Adabas Nucleus Messages and Codes" for more
information. Contact your database administrator. |
| Text | Internal error. DB/FNR/Net-Work ID .../.../.... |
| Expl. | The logical ID is greater than 255. |
| Actn. | Contact your database administrator. |
| Text | Internal error. DB/FNR/Net-Work ID .../.../.... |
| Expl. | An invalid ID table index detected in the user buffer. |
| Actn. | Contact your database administrator. |
| Text | Invalid I/O buffer for internal Adabas command. DB/FNR .../.... |
| Actn. | Contact your database administrator. |
| Text | ID table not found. DB/FNR/Net-Work ID .../.../.... |
| Expl. | The Adabas installation procedure was not properly executed, especially the Adabas SVC. |
| Actn. | Inform your database administrator. |
| Text | Internal command issued from ADA V4 ADALINK. DB/FNR .../.... |
| Actn. | Contact your database administrator. |
| Text | Adabas version inconsistency. DB/FNR .../.... |
| Expl. | SVC 04/16 call received from Adabas Version 4 ADALINK, with Adabas Version 5 user buffer or AMODE=31. |
| Actn. | Contact your database administrator. |
| Text | Command rejected. DB/FNR .../... Net-Work ID .... |
| Expl. | The command has been rejected by the Adabas user exit. |
| Actn. | Contact your database administrator. |
| Text | Command rejected. DB/FNR .../... Net-Work ID .... |
| Expl. | The command has been rejected by the Adabas user exit. |
| Actn. | Contact your database administrator. |
| Text | Response code from Link Routine. DB/FNR/Subc .../.../.... |
| Expl. | Response code from the Link Routine. DB/FNR/Subc .../.../.... For the detailed reason, see the subcode. |
| Actn. | Contact your database administrator. |
| Text | Response code from ATM. DB/FNR/Subcode .../.../.... |
| Expl. | This response code should only occur when Adabas Transaction
Manager is being used. 2 The global transaction does not have the status that allows the call. 3 No transaction ID (XID) entries exist. 4 The "R" and "J" options are not supported; or this is not a global transaction. The transaction ID (XID) either does not exist or cannot be found (for example, when the given XID does not belong to the UQE). 5 The record or value buffer definition may be invalid (for example, the length size may be invalid); or the value buffer content may be invalid (for example, it may not contain a valid transaction ID (XID)). 6 The user is not an update or ET user or is already involved in a global transaction. For further subcodes, see the Adabas documentation |
| Actn. | For further subcodes, see the Adabas documentation Check program
and correct error. |
| Text | Receiving/relay node unable to allocate buffer. DB/FNR .../.... |
| Expl. | The receiving/relay node was unable to allocate a buffer to read the command. If this response is recurrent, the size of the receiving/relay node"s attached buffer pool should be increased (see the execution parameter "NAB" in the Net-Work CTCS documentation). The ACBADD2 field in the Adabas control block contains the ID of the node in error in the leftmost 2 bytes. |
| Actn. | Increase the size of the short term buffer allocated on the BUFFER parameter of the NODE statement, or contact your database administrator. |
| Text | Receiving node intercepted ABEND during SVC 4-call.DB/FNR .../.... |
| Expl. | The receiving node intercepted an abnormal termination during the Adabas SVC 4-call for the command. |
| Actn. | Contact your database administrator. |
| Text | No CQE could be allocated on a relay node. DB/FNR .../.... |
| Expl. | No CQE could be allocated on a relay node (same as Natural error NAT3151 on a receiving node). |
| Actn. | Contact your database administrator. |
| Text | CTCS response code: node loop. DB/FNR .../.... |
| Actn. | Contact your database administrator. |
| Text | Adabas command timed out by receiving/relay node. DB/FNR .../.... |
| Expl. | The Adabas command has been timed out by the receiving/relay
node. The request waited for a reply for a longer time period than specified by the REPLYTIM= parameter in either the NODE statement or the SET operator command. The reply may be delayed or lost due to a target malfunction or a connecting link failure. Only the setting ADAMODE=0 of the Natural profile parameter ADAMODE is supported by Entire Net-Work. |
| Actn. | Check all connections and correct error, check setting of Natural profile parameter ADAMODE, or contact your database administrator. |
| Text | Response code from Entire Net-Work. |
| Expl. | Response code from Entire Net-Work. |
| Actn. | See the Entire Net-Work documentation for more information on the meanings and use of these response codes. |
| Text | Response code from Entire Net-Work. |
| Expl. | Response code from Entire Net-Work. |
| Actn. | See the Entire Net-Work documentation for more information on the meanings and use of these response codes. |
| Text | Response code from Entire Net-Work. |
| Expl. | Response code from Entire Net-Work. |
| Actn. | See the Entire Net-Work documentation for more information on the meanings and use of these response codes. |
| Text | SVC or database not UES-enabled. DB/FNR/Subcode .../.../.... |
| Expl. | ADALCO is UES-enabled, but - the SVC is not UES-enabled (the subcode in Additions 2 is x"01"), or - the target database is not UES-enabled (the subcode in Additions 2 is x"02"). |
| Actn. | Make sure that Adabas and the SVC are at the V712 level and that the database is UES-enabled. |
| Text | Command queue element ignored, user already active.DB/FNR .../.... |
| Actn. | Try again later or cancel current user. |
| Text | Protocol violation of X/Open XA specification. DB/FNR .../.... |
| Expl. | The protocol defined by the X/Open XA specification has been violated. This happens, for example, if a user tries to issue an ET call for an XA transaction. |
| Actn. | Follow the XA specification. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | Response code from Adabas user exit. |
| Expl. | This response code is assigned in an Adabas user exit, and its
meaning is defined by the user. One example is the response code in the ADALOG log data field issued by user exit 4. |
| Actn. | Refer to the description of user exits in the Adabas User Exits documentation for more information. |
| Text | ATM encountered error .... DB/FNR/Subcode .../.../.... |
| Expl. | ATM encountered an error. The error code can be found in the Additions 2 field of the Adabas control block. The response code may be in the first two bytes of the Additions 2 field. |
| Actn. | Check the meaning of the error code. If the cause of the problem is not apparent, contact your Software AG technical support representative. |
| Text | ATM received response code .... DB/FNR/Subc. .../.../.... |
| Expl. | ATM received an unexpected Adabas response code. The subcode and response code can be found, in that order, in the Additions 2 field of the Adabas control block. If a negative value appears in the Additions 2 field, take its complement: this is the response code returned to the proxy by ATM. For non-mainframe systems, see the Adabas documentation for response codes. |
| Actn. | Check the meaning of the Adabas response code and subcode. If the cause of the problem is not apparent, contact your Software AG technical support representative. |
| Text | ATM transaction status error .... DB/FNR/Subcode .../.../.... |
| Expl. | ATM or the TM proxy was unable to determine the status of the caller"s transaction. There might be an ATM error code in the Additions 2 field of the Adabas control block, in the low-order (rightmost) two bytes. For non-mainframe systems, see the Adabas documentation for response codes. |
| Actn. | Check the meaning of the error code, if present. Otherwise, determine the status of the transaction using online services. If the action required is not apparent, contact Software AG support. |
| Text | ATM unsolicited syncpoint request. DB/FNR/Subc. .../.../.... |
| Expl. | ATM or the TM proxy received an unsolicited syncpoint request. The action taken or the status of the global transaction that was open is indicated by a subcode in the Additions 2 field of the Adabas control block, in the low-order (rightmost) two bytes. For non-mainframe systems, see the Adabas documentation for response codes. |
| Actn. | Review the TMSYNCMGR and TRNCTL parameters in the ATM parameter module. |
| Text | Response code returned by Adabas Transaction Manager. |
| Expl. | Response code returned by Adabas Transaction Manager. |
| Actn. | See the Adabas Transaction Manager documentation for more information. |
| Text | Response code from COR. DB/FNR/Subcode .../.../.... |
| Expl. | This response code is issued for communication problems between
add-on products that use the system coordinator (COR) interface to Adabas; that is, Adabas Fastpath, Adabas Vista, Adabas SAF Security, and Adabas Transaction Manager. 1 Internal error. 2 A required module could not be loaded. This is probably an installation error. |
| Actn. | For subcode 1, contact your Software AG technical support representative. For subcode 2, consult the installation instructions for the add-on product. |
| Text | Utility communication block (UCB) overflow. DB/FNR .../.... |
| Expl. | Utility communication block (UCB) overflow. |
| Actn. | Contact your database administrator. |
| Text | Correct ID not found in communication block. DB/FNR .../.... |
| Expl. | Correct ID not found in the utility communication block. |
| Actn. | Contact your database administrator. |
| Text | Response code from Adabas Vista. DB/FNR .../... Subcode .... |
| Expl. | See the product documentation for more information. |
| Actn. | Proceed as indicated in the documentation. |
| Text | The ACBX validation failed. DB/FNR/Subcode .../.../.... |
| Expl. | The ACBX validation failed. The following subcodes are possible: Subcode Description 1 Unsupported ACBX version. 2 ADACBX provided without UBE. 3 ACBX file number > 65,535. 4 Reserved field not zero. 5 ACBX length incorrect. |
| Actn. | Contact your database administrator. |
