Text |
Error using Adabas add-on product. DB/FNR/Subcode .../.../.... |
Explanation |
An error has occurred using one of the client-based Adabas add-on products such as Adabas System Coordinator, Adabas Fastpath, Adabas Vista, Adabas Transaction Manager, or Adabas SAF Security. Subcodes 1-20 are generated by Adabas Fastpath. Subcodes 21 and above are generated by Adabas System Coordinator. Please refer to the documentation for the appropriate add-on product for further information on subcodes and console messages that can help you resolve the error. |
Action |
Proceed as indicated in the respective documentation. |
Text |
Space calculation error. DB/FNR .../.... |
Action |
Retry the OPEN operation. |
Text |
Record buffer specified in CB too small. DB/FNR .../.... |
Explanation |
The Prefetch record buffer, as specified in the user control block, is too small. |
Action |
Contact your database administrator. |
Text |
GETMAIN error or not enough space for Prefetch. DB/FNR .../.... |
Explanation |
When performing Prefetch, either a GETMAIN error occurred or there was not enough space available. Prefetch is switched off. |
Action |
Contact your database administrator. |
Text |
Command ID active on another database. DB/FNR .../.... |
Explanation |
The specified command ID is already active on another database for this user. |
Action |
For more information, please refer to the Adabas documentation. |
Text |
The Command ID pool is full. DB/FNR .../.... |
Action |
Increase the size of either or both the ADARUN NQCID or NU parameters. |
Text |
The specified ISN was invalid. DB/FNR/Subcode .../.../.... |
Explanation |
Possible reasons: - An HI command was issued with an ISN less than MINISN. - An N2 command was issued with an ISN either equal to 0 or greater than the MAXISN in effect for the file. - An N2 command was issued and the specified ISN was assigned to another record in the file. - An A1/A4, L1/L4, E1/E4 or S1/S2/S4 (with FB) command was issued for a non-existent ISN. - Subcode 249 is given only when Adabas Vista is in use. See the Adabas Vista documentation for more information. |
Action |
Check program and correct error, or contact your database administrator. |
Text |
DELETE command executed with ISN=0. DB/FNR/Subc .../.../... |
Explanation |
A DELETE command (E1) was executed, but the ISN specified is zero. For more information, see the Adabas documentation. |
Action |
Contact your database administrator. |
Text |
Error from Adabas cluster service. DB/FNR/Subcode .../.../.... |
Explanation |
An error was reported by the Adabas cluster messaging service on the sender"s side. The message was not sent. One of the following subcodes may be present: 4 No valid destination(s). 8 Too many destinations. 12 Invalid message type. 16 Invalid environment. 20 Send buffer length exceeded. 24 Receive buffer length exceeded. 28 No replies or acknowledgement(s). 32 Unable to allocate AXMCB. 36 Timed out on originating system. 40 Timed out on destination system. Further possible subcodes can be found in the Adabas documentation. |
Action |
Further possible subcodes can be found in the Adabas documentation. If you are unable to resolve the problem, contact your Software AG technical support representative. |
Text |
Error from Adabas cluster service. DB/FNR/Subcode .../.../.... |
Explanation |
An error was reported by the Adabas cluster messaging service on the receiver"s side. The message was sent. One of the subcodes described for response code 123 may be present. |
Action |
If you are unable to resolve the problem, contact your Software AG technical support representative. |
Text |
Internal error from one cluster nucleus. DB/FNR .../.... |
Explanation |
An internal error occurred when one cluster nucleus attempted to issue an inter-nucleus command to one or more of the other cluster nuclei. This condition usually leads to an abnormal termination. For an explanation of this response code for non-mainframe databases, see the Adabas documentation. |
Action |
Contact your Software AG technical support representative. |
Text |
Error during inter-nucleus communication. DB/FNR .../.... |
Explanation |
A messaging error occurred during inter-nucleus communication: - The nucleus did not respond within the allotted time (see the ADARUN MXMSG parameter); or - one or more problems occurred in what could be a broadcast; that is, a communication with multiple targets. In this case, each individual ACB contains either response code 0, 123 or 124. |
Action |
If you are unable to resolve the problem, contact your Software AG technical support representative. |
Text |
Attempt to perform unsupported function. DB/FNR .../.... |
Explanation |
In an Adabas cluster environment, the user attempted to perform an Adabas function that is not yet supported by Adabas cluster nuclei. |
Action |
Do not attempt to perform an unsupported function. |
Text |
Error in an Adabas cluster environment. DB/FNR/Subc .../.../.... |
Explanation |
An error indicated by one of the following subcodes occurred in an Adabas cluster environment: 1 A user table entry (UTE/PLXUSER) was not found in the MPM 8 call. 2 A user table entry (UTE/PLXUSER) was not found in the MPM 12 call. 9 The associated PLXUSER(UTE) was unsuitable at command initiation. 10 The associated PLXUSER(UTE) was unsuitable at command completion. For more information, please refer to the Adabas documentation. |
Action |
Contact your Software AG technical support representative. |
Text |
Replication-related error .... DB/FNR/Subc. .../.../.... |
Explanation |
During Adabas Event Replicator processing, a response code qualified as shown in the error message was returned. The subcode indicates the reported error condition. See the "Replication Response Codes" section of the Event Replicator documentation. |
Action |
The appropriate reaction depends on the specific error condition indicated by the response subcode, as given in the documentation. |
Text |
Error while processing LOB-file. DB/FNR/Subcode .../.../.... |
Explanation |
An error occurred while Adabas was reading or updating a LOB file. See the Adabas documentation for the explanation of the subcode. |
Action |
Contact your database administrator. |
Text |
Replication processing error. DB/FNR/Sub .../.../.... |
Explanation |
An error was detected when an attempt was made to replicate a compressed record. The subcode identifies the kind of error: 1 The function is not permitted for this type of file. The file is an LOB file. 2 The compressed input record length is invalid. 11 The record structure is invalid. 12 An invalid elementary empty field was encountered. The structure does not agree with the FDT definition. 13 An invalid multiple-value field count was encountered. 14 An invalid periodic group count was encountered. 15 An invalid structure of an elementary field was encountered. |
Action |
Check program and correct error. |
Text |
Error while creating system fields. DB/FNR/Subc .../.../.... |
Explanation |
An error was detected when creating system fields. |
Action |
Check program and correct error. |
Text |
Adabas Auditing error. DB/FNR/Sub .../.../.... |
Explanation |
An error was detected when a function was requested of an Adabas Auditing Server or Adabas executing with AUDIT=YES. The subcode identifies the kind of error: 72 DB not defined as auditing server 81 Subscription already active 73 Invalid subfct detected by Adabas 82 Subscription not activated 74 Destination not defined 83 Subscription already inactive 75 Destination already active 84 Subscription not deactivated 76 Data on SLOG, dest not activated 85 Open destination failed 77 Destination not activated 86 Destination is not closed 78 Destination already inactive 87 Close destination failed 79 Destination not deactivated 88 Destination is not open 80 Subscription not defined |
Action |
Check function request and correct error. |
Text |
A requested lock could not be granted. DB/FNR .../.... |
Explanation |
A requested lock could not be granted, because a deadlock situation was detected. |
Action |
Contact your database administrator. |
Text |
The specified ISN was not in "hold" status. DB/FNR .../.... |
Explanation |
The ISN specified with an UPDATE command was not in "hold" status for the user. |
Action |
Check program and correct error, or contact your database administrator. |
Text |
Record not available at present. DB/FNR/Subc :1:/:2:/:3: (:4:). |
Explanation |
1. An Adabas call attempted to read a record which was already in
hold status for another user for subsequent updating or upgrading
the hold status.
The origin and the ISN are shown as (JOBNAME/USERID/ETID/ISN).
Information about the origin and ISN is available as of
Adabas Version 8.2 and the database must be started with an ADARUN
INFOBUFFERSIZE parameter greater than "0".
2. The hold queue has overflowed.
|
Action |
See RETRY statement in the Natural documentation. See Adabas documentation for the explanation of subcodes. |
Text |
Invalid buffer length. DB/FNR/Subcode .../.../.... |
Explanation |
An invalid buffer length was detected by the Adabas interface routine.
The subcode identifies the buffer type:
Subcode Buffer Type
1 Format buffer
2 Record buffer
3 Search buffer
4 Value buffer
5 ISN buffer
6 User information buffer
7 Performance buffer
8 Multifetch buffer
|
Action |
Contact your database administrator. |
Text |
ISN invalid: negative or greater than maximum ISN. DB/FNR .../.... |
Explanation |
The ISN was invalid. The ISN transformation resulted either in a negative ISN or in an ISN which was greater than the maximum ISN permitted for the file. |
Action |
Contact your database administrator. |
Text |
Database ...,Net-Work ID ... currently not active. Subc .... |
Explanation |
The database which Natural or a Natural program tried to access was not active or not accessible when the attempt was made. For more information, please refer to the Adabas documentation. |
Action |
Start the database or contact your database administrator. |
Text |
Communication error detected. DB/FNR/Subcode .../.../.... |
Explanation |
A communication error was detected. The Subcode field contains the system service completion code which caused the error response. |
Action |
Contact your Adabas administrator. |