Author: Robert Sample
Posted: Tue Sep 20, 2016 5:32 pm (GMT 5.5)
Your post is as clear as mud. You seem to be asking at least two separate and different questions:
Have you looked at the EIB data to see if it provides what you want? Furthermore, WHAT other ABENDS are you seeing -- an AICA is very different than an ASRA and should be handled differently, just for one example?
You had not previously mentioned that the program stops working, so is this a separate issue? Furthermore, "stops working" is a waste of typing -- do you mean that the transaction abends? the program disappears from CICS without a transaction abend? the program is running but not responding to socket data? the program is running and responding to socket data but doing so incorrectly? or some other "stops working" condition you haven't explained?
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Tue Sep 20, 2016 5:32 pm (GMT 5.5)
Your post is as clear as mud. You seem to be asking at least two separate and different questions:
| Quote: |
| 1. Is it possible to get some Abend details in our abend routine |
Have you looked at the EIB data to see if it provides what you want? Furthermore, WHAT other ABENDS are you seeing -- an AICA is very different than an ASRA and should be handled differently, just for one example?
| Quote: |
| 2. It would help a lot to analyse why after some hours the program stops working. |
You had not previously mentioned that the program stops working, so is this a separate issue? Furthermore, "stops working" is a waste of typing -- do you mean that the transaction abends? the program disappears from CICS without a transaction abend? the program is running but not responding to socket data? the program is running and responding to socket data but doing so incorrectly? or some other "stops working" condition you haven't explained?
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth