The following decimal abend (abnormal end) codes occur in various Adabas modules as detailed below.
When message ADAM99 appears, both the system and nucleus abend codes are presented in hexadecimal. In this case, you must first change the nucleus abend code to decimal before looking up the description here.
Most abend codes (except 20) result from errors that normally require assistance from your Adabas support technical representative. If abend codes 23 or 24 occur, save the Work data set. For all abend codes, save any dumps and note any messages or other indications that the system issues. Advise your Adabas technical support representative of the error.
Note:
Entire Net-Work issues only the abend code 253 to indicate an
abnormal termination occurred. The abend (abnormal end) codes described in this
document are issued primarily by Adabas modules operating with Entire
Net-Work. Specific information related to an error is given in the messages
written to the print data set.
Code | Module | Explanation |
---|---|---|
15 | (nucleus) | Workpool too small to execute session autorestart. |
16 | (nucleus) | DTP=RM: Two-phase commit logic error. |
17 | (nucleus) | DTP=RM: Work-part-4 overflow. |
19 | (nucleus) | DTP=RM: Two-phase commit logic error. |
20 | (nucleus) | Error during system startup (refer to descriptions of nucleus startup errors in Adabas Messages and Codes). |
21 | (nucleus) | I/O error during asynchronous buffer flush (Asso/Data/Work/PLOG). |
22 | (nucleus) | I/O error on sequential PLOG and PLOGRQ=YES/FORCE in effect. |
23 | (nucleus) | WORK overflow. |
24 | (nucleus) | Autostart canceled - protection area inconsistent. |
25 | (nucleus) | Logical I/O error: Adabas was unable to track one or more I/O operations). |
26 | (nucleus) | Adabas session canceled by operator command. |
27 | (nucleus) | Session ended due to work pool space problems. |
28 | (nucleus) | Nucleus problem during an asynchronous buffer flush. |
29 | (nucleus) | Adabas Transaction Manager (ATM) initialization failed. Review the console messages for further information about the error. |
30 | (nucleus) | Adabas Transaction Manager (ATM) interface error. |
31 | (nucleus) | Insufficient workpool space for only active command. |
32 | (nucleus) | Internal error processing search algorithm 3 command. |
33 | (nucleus) | Logic error during file number validation. |
33 | ADARAC | Recovery Aid logic error. |
34 | utilities | Abnormal termination with dump. |
35 | utilities | Abnormal termination without dump. |
36 | utilities | I/O error occurred while writing to DDDRUCK or DDPRINT. Check JCL. |
37 | (nucleus) | ET post logic error. |
38 | (nucleus) | Unexpected response code for internal command. |
39 | (nucleus) | Fatal internal response code occurred during asynchronous buffer flush. |
40 | (nucleus) | Getmain failure early during session start. |
40 | ADACOM | Fatal error during ADACOM processing (cluster environments). |
41 | ADADSFN | Fatal error during Delta Save Facility processing. |
42 | (nucleus) | A security violation occurred at startup. |
43 | (nucleus) | Logic error in command selection (freeze table). |
44 | (nucleus) | Logic error in an FST write or an online process. |
45 | (nucleus) | Logic error in asynchronous buffer flush by volume (with ASYTVS=YES) |
46 | (nucleus) | Logic error in the buffer pool manager. |
47 | (nucleus) | Logic error in thread management |
48 | (nucleus) | Logic error in ADANCX (cluster environments). |
49 | (nucleus) | General internal error (various reasons) |
50 | (nucleus) | Logic error in SRB code (Adabas Cluster Services) |
51 | (nucleus) | Logic error in dynamic Work access |
52 | (nucleus) | STCK clock not running |
53 | (nucleus) | Logic error in global hold queue element lock handling |
54 | (nucleus) | Logic error in global file lock handling |
55 | ADACLU | Fatal error during ADACLU processing (cluster environments). |
56 | (nucleus) | Logic error in ET synchronization process |
57 | (nucleus) | Unexpected error during online recovery |
58 | (nucleus) | Error in protection record bookkeeping |
59 | (nucleus) | Logic error during large object (LB) processing |
60 | (nucleus) | Unique descriptor update logic error |
61 | (nucleus) | Logic error in system field update |
65 | (replication) | Fatal error related to replication processing. |
66 | (replication) | Logic error in initial-state processing |
67 | (replication) | Logic error in SLOG handling |
70 | (nucleus) | Parallel Services nucleus canceled by peer nucleus |
71 | (nucleus) | Logic error or bad data in protection data area extension on Work data set |
72 | (nucleus) | Logic error in protection data publishing |
79 | (nucleus) | Uncorrectable intracluster communication failure |
80 | (nucleus) | Logic error in update tracking |
82 | (nucleus) | Logic error in file activity bookkeeping |
83 | (nucleus) | Logic error in extended MU/PE handling |
84 | (nucleus) | Logic error in spanned record handling |
85 | (nucleus) | Logic error in spanned record read-lock handling |
86 | (nucleus) | Logic error in Adabas Fastpath multifetch processing |
87 | (nucleus) | Logic error in multiple buffers |
89 | (nucleus) | Logic error during global update command synchronization |
90 | (nucleus) | Logic error when updating a compressed record |
91 | (nucleus) | Internal error |
92 | (nucleus) | Logic error during increase of an address converter extent |
93 | (nucleus) | Logic error when processing an online function |
94 | (nucleus) | Logic error in special descriptor decompression |
95 | (nucleus) | Logic error during AAD, AA handling |
96 | (nucleus) | Logic error in command selection |
108 | ADATRA | Failure to load and install the trace module |
109 | ADAZIP | Fatal error related to the execution of Adabas code on a System z Integrated Information Processor (zIIP) |
245 | ADAMPM | Error locating ADAIOR in ESTAE recovery routine |
247 | ADAMPM | Unsuccessful ESTAE |
248 | ADAMPM | Invalid operating system or RMODE. If the nucleus is running AMODE 31, then RMODE 24 was not set for at least one Adabas module other than ADALNK. |
249 | ADAMPM | Invalid function |
252 | ADAIOS | Unrecoverable subtask abend. See the ADAM90 message description. |
253 | ADAMPM | Nonrecoverable abend. See the ADAM99 message description in Adabas Messages and Codes. |
254 | ADAMPM | Invalid function in abnormal termination exit |
255 | ADAMPM | Invalid function |
485 | ADALCO | Unsupported function |
ADALNI | ||
ADALNK | ||
486 | ADASVC | Invalid PCR04 call |
487 | ADASVC | Caller specified an unknown or invalid target. This is possibly caused by restarting an already active target using FORCE=YES. |
488 | ADASVC | Invalid PCR16 call |
489 | ADASVC | Invalid 48-call parameters |
490 | ADASVC | Target ID table may only be changed by a communicator |
491 | ADASVC | SVC 12-call without 16-call required |
493 | ADASVC | Invalid 00-call parameters |
494 | ADASVC | Caller not authorized |
496 | ADASVC | No IDT |
497 | ADASVC | Invalid function |
498 | ADALCO | Invalid UB |
ADALNI | ||
ADALNK | ||
499 | ADALCO | Length of user info less than zero |
ADALNI | ||
ADALNK | ||
500 | ADALNI | Error in link initialization routine |
501 | ADALCO | Incorrect router version |
ADALNI | ||
ADALNK | ||
502 | ADALCO | User exit before-call increased length of user info |
ADALNI | ||
ADALNK | ||
515 | ADAIOS | Storage allocation processing error |
516 | ADAIOS | I/O event completion processing error |
517 | ADAIOS | Unexpected I/O response code |
519 | ADAIOS | I/O control block allocation error |
545 | ADAIOS | Storage error building I/O parameters |
547 | ADAIOS | z/OS level unsupported |
548 | ADAIOS | Unsupported disk device type |
549 | ADAIOS | Error removing event control block from list |
550 | ADAIOS | Operator command processing error |
551 | ADAIOS | I/O control block error |
560 | ADAIOS | Maximum blocks/track > minimum, global sequential block size too large or invalid event count |
561 | ADAIOS | Error processing events |
577 | ADACICS | User exit before-call increased length of user info |
580 | ADACICS | Length of user info less than 0 or greater than 32K |
581 | ADACICS | Incorrect router version |
582 | ADACICS | Invalid UB |
583 | ADAIOS | Error initializing operator communications |
584 | ADACICS | Unsupported function |
619 | ADACICS | Invalid SVC number in link routine |
620 | ADAIOS | Error processing call to ADAIOR |
628 | ADAIOS | Storage allocation error during initialization |
636 | LNCSTUB | CICS TWA not available |
637 | LNCSTUB | CICS request failed |
643 | ADACICS | Communications area invalid |
645 | ADACICS | Error processing wait request |
649 | ACITMZ | CICS TWA not present or too short |
ADACICS | ||
652 | ADACICS | Invalid parameter list |
ADALCO | ||
ADALNI | ||
ADALNK | ||
653 | ADACICS | Error processing wait request |
656 | ADALNI | An internal error occurred when the IMS link routine attempted to set the value for the userid (the last eight bytes of the 28-byte Adabas communication ID). If this user abend occurs, contact your Software AG support representative and provide a dump including the registers at time of the abend. |
657 | ADACICS | Dynamic SVC lookup table missing |
ADALCO | ||
ADALNI | ||
ADALNK | ||
658 | ADACICS | LNKUES module not available to ADALNK |
ADALCO | ||
ADALNI | ||
ADALNK | ||
659 | ADASVC | PC routine invoked by invalid caller |
661 | ADASVC | Name/Token service error |
663 | LNCSTUB | DCI initialization failed |
664 | ADASVC | SVC incompatible with install program |
665 | ADASVC | Invalid SVC caller |
666 | ADASVC | Invalid AB deallocation length |
667 | ADASVC | Unsupported z/OS release or missing CPU features |
668 | ADACICS | A syncpoint operation was triggered by an Adabas command, but the user's communication ID was not known |
669 | ADASVC | Shared 64-bit recovery routine manager error |
670 | ADACICS | The CICS EXTRACT command used to obtain the Adabas Task Related User Exit (TRUE)
global work area failed. The CICS environment is not correctly established.
Refer to the ADAK* installation messages issued during CICS start-up to see if there are any messages relating to an unsuccessful installation. |
672 | ADASVC | IDT extension not provided. Possible incorrect version of ADASIR |
673 | ADASVC | Invalid PCRCLU caller |
674 | ADALNI | An Adabas call using the ACBX has been made, but the link routine did not detect a valid reentrancy token in the parameter list. |
ADALNK | ||
675 | ADACICS | ADL consistency exit not linked |
676 | ADALNI | The work area passed to an Adabas link routine in the direct call was invalid or the attempt to obtain storage for the work area failed. |
ADALNK | ||
677 | ADACICT | CICS GETMAIN for a UB failed |
678 | ADALCO | The Adabas link routine could not find the address of a link global table, either because it was not linked with the Adabas link routine or because an attempt to load the link globals table failed. |
ADALNI | ||
ADALNK | ||
679 | ADATMZ | Invalid header |
680 | ACITMZ | Unable to obtain work area |
ADATMZ | ||
681 | ADACICS | Insufficient SAF authorization to issue a CICS EXTRACT EXIT command. Ensure that all users of the Adabas link module have UPDATE access to the EXITPROGRAM CICS command resource identifier. |
682 | ADACICS | TRUE name cannot be located |
683 | ADALNI | Wait on multiple events not supported |
ADALNK | ||
687 | ADAIOS | Error queuing parallel request |
688 | ADAIOS | Error during a switch from SRB to TCB mode when Adabas is zIIP-enabled |
689 | ADAIOS | Error during a switch from TCB to SRB mode when Adabas is zIIP-enabled |
690 | ADAIOS | A call has been issued in SRB mode, but Adabas is not zIIP-enabled |
691 | ADAIOS | Error leaving or joining enclave |
692 | ADAIOS | Dataset allocation error |
701 | ACITMZ | Invalid ADANAME parameter |
703 | ACITMZ | Invalid TMZ header |
800 | NETSIP/OS | Invalid operating system detected - not z/OS |
801 | NETSIP/OS | Parameter error detected |
802 | NETSIP/OS | Addressing or residency mode, authorization error or operating system is not a virtual machine guest |
803 | NETSIP/OS | Error detected during program loading or validation |
804 | NETSIP/OS | Space allocation failure |
806 | NETSIP/OS | NETSIR initialization failed |