Agreed! Especially if you compile with GONUM. Sometimes, you do need to
dig a bit deeper. For this I use Fault Analyzer which has a fastly
superior UI compared to IPCS. I only crack open IPCS
when I need to format control blocks or read the systrace.
On 2020-06-22 1:08 AM, Charles Mills wrote:
+1 !!!
Look at the LE or C runtime options books and get yourself a CEEDUMP.
Debugging from one is a little bit of a learning exercise of its own but FAR
superior to SYSUDUMP for 9 out of 10 (or perhaps 99 out of 100) C runtime
errors. You will get the exact line number of the offending source
statement, and the call trace of how you got there, perhaps some relevant
variables, and a hex dump of the field that gave you the S0C4 (although that
last one may require a little looking).
Purists may object. Yeah, if you are a hardcore MVS debugger, go for it with
IPCS. (But if the OP were a hardcore MVS debugger, he would not have written
the query that he did.)
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Don Poitras
Sent: Sunday, June 21, 2020 3:40 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Reading a dump
Since the program is written in C, SYSUDUMP really isn't the easiest place
to look for info.
CEEDUMP will show the regs and a traceback which is usually all that's
needed. See TERMTHDACT
option for how to generate a CEEDUMP.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
