Sorry, This is a batch job, executing a COBOL Program, it looks like the program is doing an internal sort using syncsort. I can see in the dump the statement failing is a ZAP, but also say a S0C4 abend before the S0C7 abend. It seemed to me that the registers associated with the ZAP were bad. The programmers are going to re-compile the program and test again.
Norma Mowry DECC-Mechanicsburg Operating Systems Support (ESB11) (717)-605-7865 DSN:430 e-mail address: [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Comstock Sent: Wednesday, July 03, 2013 08:44 To: [email protected] Subject: Re: Question on how to debug S0C7 (data exception) abend 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
