AEIA
Explanation
The EXEC interface program issues an abend when an exceptional condition has occurred but the command does not have the RESP option (or NOHANDLE option), or the application program has not executed an EXEC CICS HANDLE CONDITION command for that condition. This will cause DFHEIP to take the system action for the condition in question. In most cases, the system action will be to abend the transaction.
Because of their similar characteristics, the above-named abend codes for the EXEC interface program are described as a group. The codes and their corresponding exceptional conditions are as follows:
| Code | Condition |
|---|---|
| AEIA | ERROR |
| AEID | EOF |
| AEIE | EODS |
| AEIG | INBFMH |
| AIEH | ENDINPT |
| AEII | NONVAL |
| AEIJ | NOSTART |
| AEIK | TERMIDERR |
| AEIL | FILENOTFOUND |
| AEIM | NOTFND |
| AEIN | DUPREC |
| AEIO | DUPKEY |
| AEIP | INVREQ |
| AEIQ | IOERR |
| AEIR | NOSPACE |
| AEIS | NOTOPEN |
| AEIT | ENDFILE |
| AEIU | ILLOGIC |
| AEIV | LENGERR |
| AEIW | QZERO |
| AEIZ | ITEMERR |
| AEI0 | PGMIDERR |
| AEI1 | TRANSIDERR |
| AEI2 | ENDDATA |
| AEI3 | INVTSREQ |
| AEI4 | EXPIRED |
| AEI8 | TSIOERR |
| AEI9 | MAPFAIL |
| AEXC | RESIDERR |
| AEXF | ESCERROR |
| AEXG | UOWLNOTFOUND |
| AEXI | TERMERR |
| AEXJ | ROLLEDBACK |
| AEXK | END |
| AEXL | DISABLED |
| AEXU | NOTPOSS |
| AEXV | VOLIDERR |
| AEXW | TASKIDERR |
| AEX1 | DSNNOTFOUND |
| AEX2 | LOADING |
| AEX3 | MODELIDERR |
| AEX4 | UOWNOTFOUND |
| AEX5 | PARTNERIDERR |
| AEX6 | PROFILEIDERR |
| AEX7 | NETNAMEIDERR |
| AEX8 | LOCKED |
| AEX9 | RECORDBUSY |
| AEYA | INVERRTERM |
| AEYB | INVMPSZ |
| AEYC | IGREQID |
| AEYE | INVLDC |
| AEYG | JIDERR |
| AEYH | QIDERR |
| AEYJ | DSSTAT |
| AEYK | SELNERR |
| AEYL | FUNCERR |
| AEYM | UNEXPIN |
| AEYN | NOPASSBKRD |
| AEYO | NOPASSBKWR |
| AEYP | SEGIDERR |
| AEYQ | SYSIDERR |
| AEYR | ISCINVREQ |
| AEYT | ENVDEFERR |
| AEYU | IGREQCD |
| AEYV | SESSIONERR |
| AEYX | USERIDERR |
| AEYZ | CBIDERR |
| AEY0 | INVEXITREQ |
| AEY1 | INVPARTNSET |
| AEY2 | INVPARTIN |
| AEY3 | PARTNFALL |
| AEY7 | NOTAUTH |
| AEZE | CHANGED |
| AEZF | PROCESSBUSY |
| AEZG | ACTIVITYBUSY |
| AEZH | PROCESSERR |
| AEZI | ACTIVITYERR |
| AEZJ | CONTAINERERR |
| AEZK | EVENTERR |
| AEZL | TOKENERR |
| AEZM | NOTFINISHED |
| AEZN | POOLERR |
| AEZO | TIMERERR |
| AEXP | SYMBOLERR |
| AEZQ | TEMPLATERR |
| AEZR | NOTSUPERUSER |
| AEZS | CSDERR |
| AEZT | DUPRES |
| AEZU | RESUNAVAIL |
| AEZV | CHANNELERR |
| AEZW | CCSIDERR |
| AEZX | TIMEDOUT |
| AEZY | CODEPAGEERR |
| AEZZ | INCOMPLETE |
| AEZ1 | APPNOTFOUND |
System action
The transaction is abnormally terminated with a CICS transaction dump.
User response
Change the application program either to prevent the condition recurring, to check it by using the RESP option, or to handle the condition when it does occur (by using the EXEC CICS HANDLE CONDITION command). If necessary, use the contents of the EIBRESP2 field or the EIBRCODE in the EIB to assist in determining the cause of the exceptional condition.
Problem determination
The function code of the command that produced the exceptional response and the response code can be found in the EXEC interface block (EIB). The EIB is part of a larger control block, used by DFHEIP, known as the EXEC interface storage block (EIS). The EIS is addressed by the TCAEISA, which is the system part of the TCA + X'90' The EIB is pointed to from the EIS + X'8'.
The function code may be located at offset X'1B' in the EIB while the response codes may be one of the following at the given offsets:
- EIBRCODE
-
X'1D'
- EIBRESP
-
X'4C'
- EIBRESP2
-
X'50'
The Application development reference gives translations of the encoded functions and their responses.
Analysis: Because these abend codes are directly related to exceptional conditions that can be specified in HANDLE CONDITION commands, the application programmer should decide whether the condition is one that should be handled by the application (for example ENDFILE), or one that requires modifications to the application or CICS tables. :i1.DFHEIP abend codes