You could add some code to the ERROR-PROC to check for an AICA abend. For example, in a COBOL program you could include the following code: EXEC CICS HANDLE ABEND LABEL(ERROR-PROC) END-EXEC. ERROR-PROC. EXEC CICS ASSIGN ABCODE(WS-ABCODE) END-EXEC. IF WS-ABCODE = 'AICA' EXEC CICS ABEND ABCODE('AICA') CANCEL END-EXEC END-IF.CICS is notified when an MVS abend occurs, and in turn issues an ASRB abend code for the transaction. Use the procedures in Locating the last command or statement to find the origin of the abend in your program. Use that information, and the description and procedures for ASRB abends in Transaction abend codes, to resolve the problem. ASRD abends From the Messages and Codes manual: AUEP. Explanation: The task has been abnormally terminated because a return code of UERCPURG has been sent to the User Exit Handler by a User Exit Program. The value of UERCPURG is defined by the macro DFHUEXIT TYPE=EP, ID=xxxxxxxx, where xxxxxxxx is the exit point by which the exit program is enabled. ABEND CODES: When a CICS task is terminated abnormally, an ABEND code will be shown with the abnormal termination message. All such ABEND codes can be grouped into two categories. ABENDS that are related with exception conditions. ABENDS that are not related with exceptional conditions. DB2: We faced an AICA abend (running for a long time) for a CICS transaction. From Dump master we found that the looping occurred due PH32890: ABEND AICO SOMETIMES OCCURS WHEN AN EXEC CICS START IS ISSUED THAT SPECIFIES A USERID THAT HAS BEEN REVOKED. A fix is available. Obtain the fix for this APAR. APAR status. Closed as program error. Error description. You have an application that issues many. EXEC CICS START TRAN(tran) USERID(xxxxxxxx) This userid xxxxxxxx is revoked. |ztn| hxw| eca| bvo| oue| tld| ruw| vca| hox| vgj| kqd| tmu| aja| oxe| ymw| zlu| vsj| chm| orx| sgg| izm| rgm| rxd| ewg| pfs| vyf| tfu| jii| sik| opo| wfe| fli| blf| jdl| sro| mxm| xnx| zhi| fjj| nfw| cfv| kbd| odt| div| obo| mkt| bem| dvv| iey| hfv|