| View previous topic :: View next topic |
| Author |
Message |
Uttank
Beginner
Joined: 12 Feb 2004
Posts: 12
Topics: 9
|
 Posted: Thu Mar 10, 2005 2:35 am Post subject: how to resolve ceedump error in cobol-batch application |
 |
|
hi,
I mostly find difficult to analyze the ceedump using the address and offset.
any body can suggest how to go thorough to this error. how we know what actual value is moving between the variables.
Thanks. |
|
| Back to top |
|
 |
programmgr
Beginner
Joined: 25 Feb 2005
Posts: 8
Topics: 0
|
| Posted: Thu Mar 10, 2005 4:25 am Post subject: |
|
|
if u have the compiler listings you can use the offset to detrmine the approximate line nbr of the program that is abending ...
in some shops abend aid helps in determing the current key ..which tells the record from the file that lead to abend
Third and most imp something i personally prefer is ..displays and xped
any othr suggestions .. |
|
| Back to top |
|
|
karunkallore
Beginner
Joined: 11 Dec 2004
Posts: 103
Topics: 39
|
| Posted: Fri Mar 11, 2005 1:54 pm Post subject: cobol code.... |
|
|
The most painful part is when the cobol code gives User abends. This will be (in most of the cases ) from the abend macro. If one can go to the assembler listing of the cobol code in listing then one can find where this abend macro is invoked with the User code ( like U0002) . Then by analysing the statements above it we can arrive at an idea of which statement is giving problem.
Mainframians please do correct me if anything wrong and due apologies for the same...
Regards,
Karun. |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
