Text |
Security violation. DB/FNR/Subcode .../.../.... |
Explanation |
Either an invalid cipher code or an Adabas or Adabas SAF Security security violation was detected. From Adabas SAF Security processing, the command could not satisfy the necessary security checks and may be accompanied by a subcode as follows: 0 A standard user check failed. 1 There is no free user file cache entry for a workstation user. 2 A cross-level security check failed. 3 No security information is available for the command. 4 A time-out occurred during a workstation logon. |
Action |
Check program and correct error, or contact your database administrator. |
Text |
The specified password was not found. DB/FNR .../.... |
Action |
Check program and correct error, or contact your database administrator. |
Text |
Incorrect Adabas password for secured file. DB/FNR .../.... |
Explanation |
The specified Adabas password does not allow you to access/update the desired Adabas-secured file. Adabas backs out any open transaction. |
Action |
Check program and correct error, or contact your database administrator. |
Text |
User not authorized to access secured file. DB/FNR .../.... |
Explanation |
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. |
Action |
Check program and correct error, or contact your database administrator. |
Text |
The password pool has overflowed. DB/FNR .../.... |
Action |
Contact your database administrator. |
Text |
Logon phase 1 completed for Adabas SAF Security. DB/FNR .../.... |
Explanation |
The Adabas SAF Security completed phase 1 of logon and requested phase 2. |
Action |
Send a phase-2 logon request to Adabas SAF Security. |
Text |
Execute a phase 1 logon. DB/FNR .../.... |
Explanation |
As an Adabas SAF Security remote user, you should execute a phase 1 logon. The logon ID and your password are sent to Adabas SAF Security. This response indicates that two-phase logon can continue. |
Action |
The platform does not have the correct Adabas link routine installed. The response code is intercepted by the workstation Adabas link routine and phase 1 logon is performed. |
Text |
Adabas SAF Security detected an expired password on the server. |
Explanation |
Adabas SAF Security detected an expired password on the server. The workstation user"s password has expired. |
Action |
For more information, please refer to the Adabas documentation. Contact your database administrator. |
Text |
Internal error. DB/FNR/Net-Work ID .../.../.... |
Explanation |
A logical ID is greater than 255. |
Action |
Contact your database administrator. |
Text |
Internal error. DB/FNR/Net-Work ID .../.../.... |
Explanation |
An invalid ID table index was detected in the user buffer. |
Action |
Contact your database administrator. |
Text |
Invalid I/O buffer for internal Adabas command. DB/FNR .../.... |
Explanation |
An invalid input/output buffer was encountered for an internal command. |
Action |
Contact your database administrator. |
Text |
ID table not found. DB/FNR/Subc/NW-ID .../.../.../.... |
Explanation |
The Adabas installation procedure was not properly executed, especially the Adabas SVC. The subcode describes the reason of the error. If you were running with Entire Net-Work, NW-ID contains the ID of the Entire Net-Work node that issued this response code. |
Action |
Contact your database administrator. |
Text |
Internal command issued from ADA V4 ADALINK. DB/FNR .../.... |
Action |
Contact your database administrator. |
Text |
Adabas version inconsistency. DB/FNR .../.... |
Explanation |
The Adabas interface used by the application program, or the Entire Net-Work version used is not supported by the Adabas nucleus. |
Action |
Contact your database administrator. |
Text |
Command rejected. DB/FNR/Net-Work ID .../.../.... |
Explanation |
The command has been rejected by the Adabas user exit. |
Action |
Contact your database administrator. |
Text |
Command rejected. DB/FNR/Net-Work ID .../.../.... |
Explanation |
The command has been rejected by the Adabas user exit. |
Action |
Contact your database administrator. |
Text |
Response code from Link Routine. DB/FNR/Subc .../.../.... |
Explanation |
Response code from the Link Routine. DB/FNR/Subc .../.../.... See the Adabas documentation for the explanation of the subcode. |
Action |
Contact your database administrator. |
Text |
Response code from ATM. DB/FNR/Subcode .../.../.... |
Explanation |
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 |
Action |
For further subcodes, see the Adabas documentation Check program and correct error. |
Text |
Request rejected by Entire Net-Work. DB/FNR/NW .../.../.... |
Explanation |
The request was rejected by Entire Net-Work due to a shortage of short term buffers. The message shows the DBID, FNR and Net-Work ID. |
Action |
For z/OS and z/VSE, increase the region size. For BS2000, check the address space limit. |
Text |
Receiving node intercepted ABEND during SVC 4-call.DB/FNR .../.... |
Explanation |
The receiving node intercepted an abnormal termination during the Adabas SVC 4-call for the command. |
Action |
Contact your database administrator. |
Text |
No CQE could be allocated on a relay node. DB/FNR .../.... |
Explanation |
No CQE could be allocated on a relay node (same as Natural error NAT3151 on a receiving node). |
Action |
Contact your database administrator. |
Text |
CTCS response code: node loop. DB/FNR .../.... |
Action |
Contact your database administrator. |
Text |
Adabas command timed out by receiving/relay node. DB/FNR .../.... |
Explanation |
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. |
Action |
Check all connections and correct error, check setting of Natural profile parameter ADAMODE, or contact your database administrator. |
Text |
Response code from Server. DB/FNR/Subcode .../.../.... |
Explanation |
A command was issued from a server, such as an Adabas nucleus, to another server, such as Entire Net-Work. DB/FNR/Subcode .../.../.... The command did not complete within the prescribed time period. The issuer proceeds and no longer expects a response to the command. |
Action |
See the Entire Net-Work documentation for more information on these response codes. |
Text |
Response code from Entire Net-Work. |
Explanation |
Response code from Entire Net-Work. |
Action |
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. |
Explanation |
Response code from Entire Net-Work. |
Action |
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 .../.../.... |
Explanation |
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"). |
Action |
Make sure that Adabas and the SVC are at the V712 level and that the database is UES-enabled. |
Text |
This response code is reserved for Entire Net-Work. |
Explanation |
This response code is reserved for Entire Net-Work. |
Action |
See the Entire Net-Work documentation for further information on this response code. |
Text |
Protocol violation of X/Open XA specification. DB/FNR .../.... |
Explanation |
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. |
Action |
Follow the XA specification. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
Response code from Adabas user exit. |
Explanation |
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. |
Action |
Refer to the description of user exits in the Adabas User Exits documentation for more information. |
Text |
ATM encountered error/response .../.... DB/FNR .../.... |
Explanation |
Adabas Transaction Manager (ATM) encountered an error. The ATM error and response code are given in the message. |
Action |
Check the meaning of the Adabas Transaction Manager 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/Subcode .../.../.... |
Explanation |
The Adabas Transaction Manager (ATM) received an unexpected Adabas response code. The ATM response code and subcode are given in the message. If the ATM response code has a negative value, take ist complement: this is the response code returned to the proxy by ATM. |
Action |
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 .../.../.... |
Explanation |
The Adabas Transaction Manager (ATM) or the ATM proxy was unable to determine the status of the caller"s transaction. The ATM error code is given in the message. |
Action |
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/Subcode .../.../.... |
Explanation |
The Adabas Transaction Manager (ATM) or the client proxy received an unsolicited syncpoint request. The action taken or the status of the global transaction that was open is indicated by the subcode which is described in the Adabas documentation. |
Action |
Review the TMSYNCMGR and TRNCTL parameters in the ATM parameter module. |
Text |
Response code returned by Adabas Transaction Manager. |
Explanation |
Response code returned by Adabas Transaction Manager. |
Action |
See the Adabas Transaction Manager documentation for more information. |
Text |
Response code from COR. DB/FNR/Subcode .../.../.... |
Explanation |
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. Subcodes:
1 - Internal error.
2 - A required module could not be loaded. This is probably an
installation error.
For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.
|
Action |
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 .../.... |
Explanation |
Utility communication block (UCB) overflow. |
Action |
Contact your database administrator. |
Text |
Correct ID not found in communication block. DB/FNR .../.... |
Explanation |
Correct ID not found in the utility communication block. |
Action |
Contact your database administrator. |
Text |
Data-archiving error. DB/FNR/Subcode .../.../.... |
Explanation |
This response code is returned by Adabas data-archiving processing. See the Adabas data-archiving documentation for more information. |
Action |
Check program and correct error. |
Text |
Response code from Adabas Vista. DB/FNR/Subcode .../.../.... |
Explanation |
See the product documentation for more information. |
Action |
Proceed as indicated in the documentation. |