IBM Mainframe Forum

I am getting AEXZ abend when the user tried the trailing stop status request from XML, the request got timed out. because the process went into looping, when the same request tried again,it worked without any looping and the XML user got response. may i know the reason why it got abend at that point and also storage voilation has caused that time.

Have you tried to use the transaction dump to determine the cause or asked for help from you CICS system support people as the manual asks you to?

Can you please re-state all the information that you are trying to convey to us.

If a program is looping, it would not be unusual for something expecting a response to "time out".

If you have a "storage violation" it is possible (depending on how your CICS environment is set up) that quite a big dump is being produced somewhere, which takes some time, which might cause a user to "time out" in your scenario, which might looking like something is looping.

If you exactly re-create the situation you will get the same outcome. If you do not exactly recreate the situation you might not get the same outcome. Look at the output listing datasets for any messages which may be relevant. If you have nothing there, and have the dump available, you have to get digging.

I have no idea what a "trailing stop status request" is.

ragul, the Messages and Codes manual gives you the user response for an AEXZ abend:

Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer.

In other words, you either need to go through the transaction dump to find out what caused the problem, or if that is beyond your skill set (likely it is) you need to contact your site support group and get your CICS system programmer to look at the transaction dump for you, or to otherwise help you resolve your issue. Asking questions on a forum is, essentially, of no use at all since we do not work at your site and do not have access to your transaction dump, hence have no way to debug the issue.