Text | Error using Adabas add-on product. DB/FNR/Subcode .../.../.... |
Expl. | 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-69, 32766 and 32767 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. |
Actn. | Proceed as indicated in the respective documentation. |
Text | Space calculation error. DB/FNR .../.... |
Actn. | Retry the OPEN operation. |
Text | Record buffer specified in CB too small. DB/FNR .../.... |
Expl. | The Prefetch record buffer, as specified in the user control
block, is too small. |
Actn. | Contact your database administrator. |
Text | GETMAIN error or not enough space for Prefetch. DB/FNR .../.... |
Expl. | When performing Prefetch, either a GETMAIN error occurred or there was not enough space available. Prefetch is switched off. |
Actn. | Contact your database administrator. |
Text | Command ID active on another database. DB/FNR .../.... |
Expl. | The specified command ID is already active on another database
for this user. |
Actn. | For more information, please refer to the Adabas documentation. |
Text | The Command ID pool is full. DB/FNR .../.... |
Actn. | Increase the size of either or both the ADARUN NQCID or NU parameters. |
Text | The specified ISN was invalid. DB/FNR .../.... |
Expl. | 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 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-existent ISN. |
Actn. | Check program and correct error, or contact your database
administrator. |
Text | E1 command not allowed or specified with ISN=0. DB/FNR .../.... |
Expl. | 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 .../.../.... |
Expl. | 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. |
Actn. | 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 .../.../.... |
Expl. | 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. |
Actn. | If you are unable to resolve the problem, contact your Software
AG technical support representative. |
Text | Internal error from one cluster nucleus. DB/FNR .../.... |
Expl. | 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. |
Actn. | Contact your Software AG technical support representative. |
Text | Error during inter-nucleus communication. DB/FNR .../.... |
Expl. | 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. |
Actn. | If you are unable to resolve the problem, contact your Software
AG technical support representative. |
Text | Attempt to perform unsupported function. DB/FNR .../.... |
Expl. | In an Adabas cluster environment, the user attempted to perform
an Adabas function that is not yet supported by Adabas cluster nuclei. |
Actn. | Do not attempt to perform an unsupported function. |
Text | Internal error. DB/FNR/Subcode .../.../.... |
Expl. | 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. |
Actn. | Contact your Software AG technical support representative. |
Text | Replication-related error .... DB/FNR/Subc. .../.../.... |
Expl. | 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. |
Actn. | 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:. |
Expl. | Error while processing LB-field. DB/FNR/Subcode .../.../.... For the detailed reason see the subcode. |
Actn. | Contact your database administrator. |
Text | A requested lock could not be granted. DB/FNR .../.... |
Expl. | A requested lock could not be granted, because a deadlock situation was detected. |
Actn. | Contact your database administrator. |
Text | The specified ISN was not in "hold" status. DB/FNR .../.... |
Expl. | The ISN specified with an UPDATE command was not in
"hold" status for the user. |
Actn. | Check program and correct error, or contact your database
administrator. |
Text | Record not available at present. DB/FNR/Subcode .../.../.... |
Expl. | 1. An Adabas call attempted to read a record which was already in hold status for another user for subsequent updating. 2. An attempt was made to hold an ISN which was in hold status for another user and the R option is specified. In this case, the Additions 2 field contains the binary value 0. 3. The hold queue has overflowed. In this case, the Additions 2 field contains the binary value -1 (H"FFFFFFFF"). |
Actn. | See RETRY statement in the Natural documentation. |
Text | Invalid buffer length. DB/FNR/Subcode .../.../.... |
Expl. | 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 |
Actn. | Contact your database administrator. |
Text | ISN invalid: negative or greater than maximum ISN. DB/FNR .../.... |
Expl. | 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. |
Actn. | Contact your database administrator. |
Text | Database ...,Net-Work ID ... currently not active. Subc .... |
Expl. | The database which Natural or a Natural program tried to access was not active or not accessible when the attempt was made. For detailed information see the subcode. |
Actn. | Start the database or contact your database administrator. |
Text | Too many database nuclei used in parallel. DB/FNR .../.... |
Expl. | Too many database nuclei have been used in parallel. |
Actn. | Contact your database administrator. |