I have occasionally used SLIP+IPCS to debug an application program. The best advice I can offer is to set a SLIP trap for *any* abend. That is, do not specify an abend code. Something like
SL SET,J=xxxx,END In a complex the task environment, it's possible that the abend you see (S0C7) is a consequence of some other abend. By not specifying a code, you have a better chance of seeing the original failure. . . JO.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: Steve Comstock <[email protected]> To: [email protected], Date: 07/03/2013 05:44 AM Subject: Re: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List <[email protected]> On 7/3/2013 5:10 AM, Mowry, Norma E CIV DISA ESB (US) wrote: > We have a production job that is abending with S0C7 reason 00000007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. > > Norma Mowry > Way too little information to help. Is this batch or online? What language is it written in? What version of z/OS? Other messages around the time of the abend? etc. Kind regards, -Steve Comstock ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
