Question & Answer
Question
Why would I begin to receive AEE0 abends in several application programs after upgrading from CICS Transaction Server for z/OS (CICS TS) V4.2 to V5.2? CICS is flagging some programs with an AEE0 abend, but there have been are no known changes to the application programs.
The documentation for abend AEE0 suggests "An application that is executing in AMODE(64) called CICS using a stub program that does not support AMODE(64)". My application programs are not intentionally trying to run in AMODE(64).
Answer
Computer Associates has provided test fix TR92559 that has been successfully tested. Please contact CA Technologies for the fix.
This problem has to do with the way CA ENF hooks into the linkage from the application, through DFHERM. The application issued an EXEC DLI call. Under normal circumstances, that would go into DFHEIP and from there into DFHERM (using the address held in CSAERMNA). In this case, CA has replaced the address of both so the following occurs:
The application passed control to CA code, which gives control to DFHEIP
DFHEIP loads the address in CSAERMNA and branches to the address
This runs more CA code, which finally gives control to DFHERM
DFHEIP sets register 3 to contain the dispatcher state
DFHERM expects to receive this state in register 3, but this is corrupted by the CA code in the middle
CICS ends up with an odd value in register 3, and this causes the CICS code to mistakenly believe it has been entered in AMODE 64.
Product Synonym
CICS/TS CICSTS CICS TS CICS Transaction Server
Was this topic helpful?
Document Information
Modified date:
24 October 2016
UID
dwa1315409