It's pretty common in many shops to maintain SLIP traps to suppress dumps for most x37 abends. A dump is rarely helpful for such abends, since the cause is obvious from the abend code. For example, in IEASLP00 we have several SLIP traps like this:
SL SET,C=B37,ID=XB37,A=(NOSVCD,NOSYSU),END . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Mark Pace <[email protected]> To: [email protected], Date: 03/06/2014 11:31 AM Subject: Re: NODUMP Sent by: IBM Mainframe Discussion List <[email protected]> I kept getting a B37 space error doing a RECEIVE. IEC030I B37-04,IFG0554A,RCVPDO,SMPER1,SYSUT4,VIO , , SYS14065.T101319.RA000.RCVPDO.R0100114 I thought I was having a problem with the DSSPACE parameter, and adjusting it was making no difference. Finally I changed the DDDEF for SYSUT4 and that solved the problem. Newbies. :) On Thu, Mar 6, 2014 at 2:12 PM, Elardus Engelbrecht < [email protected]> wrote: > Gibney, Dave wrote: > > >I would favor the fix the problem approach over the suppress the > diagnostics approach. > > Indeed, because I find this statement from Mark D Pace very worrying: > > "I have a job that fails and produces a huge dump." > > What is the problem with that job? Did something changed before the job > failed? Add your usual questions and dumps/traces here for diagnostics. > > But then I see: "Good news, I fixed the problem, so no dump." > > Mark, could you be kind to tell us, if you can, what the problem was and > what fix you did? > > > Rex Pommier wrote: > > >So break it again! We want to know!! :-) > > Yes! Agreed! For us to know and for the OP to earn some easy overtime > money ... ;-) > > Groete / Greetings > Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
