Help in resolving AEXY abend.

Mainframe Application Testing, Offline testing and Tools. Xpediter, IBM Debugger.

Topic author
Aditi Patwal
New Member
Posts: 5
Joined: Wed Aug 20, 2014 8:20 am

Help in resolving AEXY abend.

Postby Aditi Patwal » Tue May 12, 2015 12:01 pm

For one of the transaction, we're getting AEXY abend code on production but the same screen does not abend and works fine in the test system. This is what I see:

Code: Select all

Transaction 'ELOA' encountered a 'AEXY' abend executing at 'O040'. This occurred at offset X'??????' in program 'ELOA543 '. Program 'ELOA543 ' starts at X'8292CFB0'.
This incident occurred for task ID '22964' at 9:25:11 on 4/21.


This further information about registers might be of use:

Code: Select all

REGS 0 - 3 00000090 01973090 006825AD 028F104C
REGS 4 - 7 00682578 00682578 01973090 01973010
REGS 8 - 11 005EF188 815554B0 00000004 013B6988
REGS 12 - 15 013B6680 8058ADC0 815556D0 835FB080

The execution transaction has been purged before control could be returned.


Could someone please guide how can I start resolving this problem.



Online
User avatar

Robert Sample
Global Moderator
Global Moderator
Posts: 1275
Joined: Fri Jun 28, 2013 1:22 am
Location: East Dubuque Illinois
Has thanked: 2 times
Been thanked: 90 times

Re: Help in resolving AEXY abend.

Postby Robert Sample » Tue May 12, 2015 5:57 pm

You start debugging by looking up the code in the Messages and Codes manual and seeing what it says. In your case, it says
AEXY


Explanation: The executing transaction has been purged before control could be returned. This can arise when the transaction is purged while
A CICS command was being processed
The transaction was waiting to be dispatched
System Action: The transaction is abnormally terminated with a CICS transaction dump.
User Response: Contact your system programmer to determine why the transaction has been purged.
So, rather than posting on a forum (which is NOT mentioned in the message), you should have contacted your system programmer (site support group) for assistance. It sounds like your production and test environments are set up differently and hence the AEXY is occurring in production. Only someone working in the site support group at your site will be able to research this issue and resolve the problem -- you cannot do this and we on this forum cannot do this.




Topic author
Aditi Patwal
New Member
Posts: 5
Joined: Wed Aug 20, 2014 8:20 am

Re: Help in resolving AEXY abend.

Postby Aditi Patwal » Thu May 14, 2015 11:03 am

Thanks Robert. Support team has sent this ticket to the developer's team to resolve. I'll ask my manage to talk to system programmer on this.




Return to “Testing Tools, Mainframe Application Testing, Abends Solution & QA.”

Who is online

Users browsing this forum: CommonCrawl [Bot] and 1 guest