Identifying the record which caused S0C7 abend

sampathkmn · New User Joined: 12 Dec 2005 Posts: 31 Location: bangalore

If a production job abends with S0C7, how to point out a particular record which caused abend(assuming input has millions of records).
I have knowledge on LIST compiler option which will point out the offset for the field which could have caused the abend. But, this won't help in pointing out exact record which might have caused it.

Is there any way apart from sing Expeditor or other debug tools?

Mathiv Anan · Active User Joined: 23 Jul 2008 Posts: 106 Location: USA

......It can be identified by counting the number of records read and displaying the record count before the program ends.

Also, a display statement would help.

dick scherrer · Posted: Thu Mar 11, 2010 10:09 am

Hello,

sampathkmn · New User Joined: 12 Dec 2005 Posts: 31 Location: bangalore

I believe offset will display only the field which is having junk/invalid data. But, how it will display the fauly data. Is there any compile parm for this?

Mathiv, I agree displaying count. but during production job monitoring SLA will not give us enough time to edit code and recompile, we can not waste time here.

enrico-sorichetti · Posted: Thu Mar 11, 2010 11:01 am

sampathkmn · New User Joined: 12 Dec 2005 Posts: 31 Location: bangalore

I am asking the way to findout S0C7 abend caused record from input. It might be one of the millions of input records.

Escapa · Posted: Thu Mar 11, 2010 11:22 am

Gnanas N · Posted: Thu Mar 11, 2010 11:32 am

And if you have File-AID or similar tools and open the input data set with copybook in File-AID, you can easily see (might be shown as INVALID) the record's field which is not obeying the field denifition of copybook.

dick scherrer · Posted: Thu Mar 11, 2010 11:44 am

Hello,

sampathkmn · New User Joined: 12 Dec 2005 Posts: 31 Location: bangalore

I saw this answer in other forum "If the cobol program is compile with option FDUMP. you can see the input record which caused the abend CEEDUMP and also the field which cause the error."

Can anyone tell if this worked?

gcicchet · Posted: Thu Mar 11, 2010 2:06 pm

Hi,

I'm no COBOL programmer, but is it also possible that a flawed process in the code can also cause the S0C7 abend such as moving fields around after tha data is read ?

Gerry

Anuj Dhawan · Posted: Thu Mar 11, 2010 3:32 pm

xpediter will take time to reach the record, do you have abend-aid installed?

Karthikeyan Subbarayan · New User Joined: 24 Feb 2008 Posts: 62 Location: Boston

Do you have abend aid in your shop .
If yes, It shows the current record in error and the previous record.. From there you skip all the millions of records until the current record using a simple SORT and you arrive at the abend record.

Robert Sample · Posted: Thu Mar 11, 2010 6:11 pm

If you got a dump (from Abend Aid or via //SYSUDUMP), you can find the current record that was being processed in the dump. If you didn't get a dump, you need to rerun and get a dump since you must have one to properly analyze the problem. As has been mentioned, however, it is not necessarily the data in the current record which caused your problem -- while a S0C7 always means invalid numeric data was processed, the source of that invalid data could be the file, your program, a subprogram, or all sorts of possibilities.