Text |
Error in Adabas FASTPATH processing. DB/FNR .../.... |
Explanation |
For explanation of this error, please refer to Adabas response code 101 in the Adabas Messages and Codes documentation. |
Text |
Space calculation error. DB/FNR .../.... |
Action |
Retry the OPEN operation. |
Text |
An Adabas STAR call was sent to an isolated database. |
Action |
Stop the database and restart it with the ADARUN parameter ADASTAR=YES or ADASTAR=NO. |
Text |
Program tried to call an Adabas STAR replicated file. |
Explanation |
The program attempted to make a logical call to a physical file defined as an Adabas STAR replicated file. |
Action |
Use only the logical file number when issuing calls. |
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 |
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 .../.... |
Explanation |
This error may have one of the following reasons: - An HI command was issued with ISN less than MINISN. - An N2 command was issued with ISN either equal to 0 or greater than the MAXISN in effect for file. - An N2 command was issued and the specified ISN was assigned to another record in file. - An A1/A4, L1/L4, E1/E4, or S1/S2/S4 (with FB) command was issued for a non-xistent ISN. |
Action |
Check program and correct error, or contact your database administrator. |
Text |
E1 command not allowed or specified with ISN=0. DB/FNR .../.... |
Explanation |
Either a Refresh File function using the E1 command was issued and not allowed or else ISN=0 was specified for the E1 command. |
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 |
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 |
Internal error. DB/FNR/Subcode .../.../.... |
Explanation |
An internal error identified by one of the following subcodes occurred
in an Adabas Sysplex cluster environment:
2 User-table entry (UTE) not found in MPM 8 call.
3 Command-queue entry (CQE) not found in MPM 8 call.
4 Intermediate user buffer (IUB) not found in MPM 8 call.
5 Adabas control block not found in MPM 8 call.
6 Invalid UTE on nucleus chain.
7 Invalid UTE on user chain add.
8 Invalid UTE on the 'lura' chain (that is, the linked list of UTEs
representing local users remotely assigned) delete.
23 Invalid CQE. |
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 LB-field. DB/FNR/Subc :1:/:2:/:3:. |
Explanation |
Error while processing LB-field. DB/FNR/Subcode .../.../.... For the detailed reason see 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 |
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 |
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 |
ISN already held by another user. DB/FNR/Subcode .../.../.... |
Explanation |
- An attempt was made to hold an ISN which was in hold status for another user and the R option is specified. - Hold queue is full and the R option is specified. - Hold queue overflow. |
Text |
Invalid buffer length. DB/FNR/Subcode .../.../.... |
Explanation |
An invalid buffer length was detected by the Adabas interface routine. |
Action |
Contact your database administrator. |
Text |
User buffer not accessible. DB/FNR/Subcode .../.../.... |
Explanation |
User buffer not accessible by the Adabas interface routine. |
Action |
Check whether the control block, format buffer, value buffer, record buffer and ISN buffer have valid addresses and lengths. Check whether the control block, ISN buffer and record buffer are write protected. |
Text |
Adabas is not active or not accessible. |
Explanation |
The Adabas nucleus was not active or not accessible when the command was issued. |
Action |
Start the database or contact your database administrator |
Text |
System communication error. |
Explanation |
A communication error was detected. The additions 2 field contains the system service completion code which caused the error response (for example, exceeded quota, no privilege). |
Action |
Check the additions 2 field. |
Text |
Too many nuclei used in parallel. DB/FNR .../.... |
Explanation |
Too many nuclei have been used in parallel. |
Action |
Do not use more than 16 different database IDs in a single program. |