|
|
| Author |
Message |
GiridharanN
New User
Joined: 12 Apr 2007
Posts: 15
Location: Coimbatore
|
|
|
|
A background CICS transaction in my shop keeps abending daily.
This is forced by a handle abend condition in the program.
But this handle abend statement occurs in a very big paragraph.
Is there any way that I can use the CICS logs to determine what part of the program causes this abend. (Say using the offset like we do in batch)
This is very difficult to simulate in test since there are infrastructural constraints. |
|
| Back to top |
|
 |
References
|
 Posted: Fri May 16, 2008 4:37 am Post subject: Re: Tracing CICS logs to determine what part causes the ABEND |
|
|
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007
Posts: 1142
Location: At my desk
|
|
|
|
Two guesses....
Promote additional displays into PROD (temporarily) or to actually debug the program and the 'dump'? |
|
| Back to top |
|
|
|
|
