For a SAD I go for the NIP messages straight off. Sometimes there are messages that could help with isolating the issue. You want something like SYSTRACE which I think is VERBEXIT SADMPMSG
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Mark Pace > Sent: Friday, February 28, 2014 6:34 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Disabled wait > > Took a SAD dump to tape. There is nothing intuitive about using IPCS. > :( I found the batch job - Prepare stand alone dump for analysis. After > that I was clueless what to do next. > > Time to RTFM. > > > On Thu, Feb 27, 2014 at 10:58 AM, Staller, Allan <allan.stal...@kbmg.com>wrote: > > > Abend COD is "an abend during abend processing" and tells you nothing. > > > > You must go to the original abend (my guess is 106-C due to storage > > failure or X78 abend). > > > > I agree. An SAD is the only way we're going to get anywhere. > > > > <snip> > > From the wait code you had a C0D abend in a task. If you look that up > > it basically tells you that a SAD will be needed and then a walk > > through the trace table data to get the real reason. > > </snip> > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
