Page 1 of 1

SOC7

Posted: Fri Jul 07, 2006 8:40 pm
by pradeepck
Hi,

Please can you advise on how can we actually find the exact field that has bad data for SOC7 abend, based on CEEDUMP and other messages.
As the line number given in SYSOUT may not be the correct location of the error data.

What exactly is offset..?

Thanks,
Deepu.

Posted: Mon Jul 10, 2006 10:57 am
by arrbee
It is not always easy to find out the exact variable that causing the S0C7 abend. The offset sometimes shows the nearest instructin that was executed and caused the abend.

You will have to use LIST, OFFSET compiler options if you need more details.

HTH.

Posted: Fri Nov 10, 2006 4:33 am
by rahul_kolhe
Do you have abendaid installed in system? You can trace it under vendor utilities.

Which will tell you the exact error location and reson like below.

*******************************************
* Error Location *
*******************************************

The next sequential instruction to be executed was at displacement
000008E2 in procedure P130_EXCEPTION_PROCESS.

*******************************************
* Analysis of Error *
*******************************************


A Data Exception is caused when a packed decimal operand has an invalid
digit (not 0-9), or its last byte contains an invalid sign (not A, B, C,
D, E, or F).

Now 000008E2 is the hex value for the statement no in the program. You can find last 3 digit 8E2(hex value) in Compile listing of the program. The problem is in previous statement.

Posted: Sun Nov 23, 2008 6:06 pm
by Anuj Dhawan
Hi,

You might like to look at this link:

http://www.mainframegurukul.com/Mainfra ... light=s0c7

And by the way, it's S0C7 (S zero C 7) not SOC7.

Topic deleted by Admin

Posted: Fri Jan 15, 2016 8:54 pm
by academyindia4
<< Content deleted By Admin >>

Topic deleted by Admin

Posted: Fri Jan 15, 2016 9:43 pm
by academyindia4
<< Content deleted By Admin >>