@Ed, this certainly goes to @Tony's point that CEEDUMP is great except when it isn't.
It's not my pig and it's not my farm but if @Janet wanted to submit a requirement I would support it. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Gould Sent: Monday, August 29, 2016 12:39 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Dump in 64 bit mode "Storage around GPR2 is invalid." > On Aug 29, 2016, at 9:51 AM, Charles Mills <charl...@mcn.org> wrote: > > Hmmm. To me, that strategy seems appropriate for a report program > ("this field is not relevant to this type of transaction so print > blanks or > asterisks") but not for a dump program. Isn't a dump -- consider the > name -- supposed to be "here it all is, as it all is, you figure out > what is relevant"? > > Is not the contents of an "irrelevant" register save area sometimes > the very clue you need? "Look at that -- it looks like part of one of > my error diagnostics -- I must be overlaying storage with the message" > or "look, R2 is pointing to my widget table. I must have come through > the widget lookup routine after all." > > I know, my comment is fundamentally irrelevant. LE's dump program > works the way it works, and they are not going to change it because of > a comment on IBM-MAIN, at least not in time to help @Janet. > > Charles Charles: Try a SHARE requirement. LE (as usual IMO) is being arrogant , They really need to be slapped down a few notches. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
