Yeah, no disagreement there. Like any of these tools that "do the work for you" they are great until they guess wrong.
Many years ago I learned to really dislike Abend-Aid. I'm sure it is a wonderful help to the average application programmer but it seemed to always obfuscate the kind of more complex ABENDs that I was shooting. (No disparagement intended to my friends at Compuware. I'm sure it's a wonderful product, and //ABNLIGN DD DUMMY solved my problem.) Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tony Harminc Sent: Thursday, August 25, 2016 1:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." On 25 August 2016 at 12:47, Charles Mills <charl...@mcn.org> wrote: > I am generally very happy with the CEEDUMP and find it quite satisfactory. My experience with CEEDUMP is that it's all just fine until it isn't. It seems not to cope at all well with anything other than a simple failure within your own code. If anything the least bit subtle happens - a stack overlay, a failure in a library routine, abend in a UNIX kernel or other z/OS system routine - it just can't be relied on to give you the information needed to find the root cause. Then you have to disable all LE exception handling, set a SLIP trap, and go back to debugging with a "real" dump. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
