IBM Mainframe Forum

Hi,
Can anyone tell me how to resolve the soc07 error.I dont have abend aid tool to identify the data which cause the abend problem. so please tel me how to find the prolem and slove the step. its big program so cant read all the lines to find the probelm. can we check the problem in program itself .is it possible

The S0C7 abend should generate some form of dump. You should be able to locate the offset in the program of the failing instruction. You should be able to take a compile of the program and find the offsets for the statements (depending upon which language you're using, of course). Locate the statement whose offset is less than the abend offset with the next statement offset higher than the abend offset. This tells you that one of the variables in that statement has an invalid numeric value.

Depending upon your level of knowledge and where the bad data is, you may be able to use the dump to directly locate the failing record (if the bad data is in a file) directly.

Is it a Cobol program giving you a S0C7?

If you look at your output in the spool, you should see a "dump" of some sort. If it is an LE dump it will tell you a displacement which you can use to find, on the Cobol output listing, which instruction is the problem. You'll probably also find an LE message in the sysout giving you the same.

So, you need to tell us what sort of DUMP you have, and whether you have the Cobol listing and whether the listing contains a reference to the source line numbers (in the listing) with a displacement (some stuff in hexadecimal).

Edit: Snap.

suppose if i wanna findout that record how to do that...

i need to find out because of which record the abend is happened...last read record how to do that...in abend aid we can find it out but without that how to do please tell me....

Sorry, but the specific answer would depend upon specifically what you got -- SYSABEND, SYSUDUMP, CEEDUMP or nothing. I know of no way that anyone at this forum could help you. You must consult with someone at your site such as a coworker, team leader, or site support group if you want assistance.

With the information we know, your best bet might be if you happen to have the key stored in the working-storage of the program.

The BLF in the data map will lead you to the file, but without knowing what dump you have, it is tricky to guide you to it.

Get to know the compile listing well, this will help you to find things in an abend.

can we get the dump values....from that we can get the exact value which cauese the abend...buz its a huge file so tracking one by one not possible at all...so how to do...in abend aid we can see that last read data...but without the abend aid how to do plese tell me.

is SYSABOUT used to capture runtime dump...if so please tell me how to use that in JCL..

Things like SYSABOUT are down to installation definition at individual sites. If you have seen that at your site, I would expect you'd get a dump on it. //SYSABOUT DD SYSOUT=* should then get a dump in the spool output. If you've seen it somewhere else, you may or may not get a dump with it - try it out, it can't cause any harm.