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.
SOC7
Moderator: Moderator Group
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.
You will have to use LIST, OFFSET compiler options if you need more details.
HTH.
Arr Bee
-------------
?My joy in learning is partly that it enables me to teach? - Seneca(Roman philosopher, mid-1st century AD)
-------------
?My joy in learning is partly that it enables me to teach? - Seneca(Roman philosopher, mid-1st century AD)
-
- Member
- Posts: 12
- Joined: Wed Nov 08, 2006 1:03 am
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.
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.
-
- Moderator
- Posts: 1625
- Joined: Sat Aug 09, 2008 9:02 am
- Location: Mumbai, India
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.
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.
Regards,
Anuj
Anuj
FREE TUTORIALS
Tutorials
Free tutorials from mainframegurukul
- JCL Tutorial
Covers all important JCL concepts. - Cobol Tutorial
This tutorials covers all Cobol Topics from STRING to COMP-3. - DB2 Tutorial
DB2 Tutorial focuses on DB2 COBOL Programming. - SORT Tutorial
This Tutorial covers all important aspects of DFSORT with examples - CICS Tutorial
This CICS tutorial covers CICS concepts and CICS Basics, CICS COBOL Programming.
Interview
Mainframe Interview questions
- Cobol Interview Questions
50+ Interview Questions - JCL Interview Questions
50+ Interview Questions - DB2 Interview Questions
100+ Interview Questions - CICS Interview Questions
70+ Interview Questions - VSAM Interview Questions
27 Interview Questions
Other References
Mainframe Tools and others
- XPEDITER Reference
Explains how we can debug a program - FILEAID Reference
Explains how to browse , edit and delete datasets - Change Man Reference
Quick Start tutorial on Changeman - Abend Reference
Important Abend codes explained - FaceBook Page
MainframeGurukul FaceBook Page - LinkedIn Page
MainframeGurkul Linkedin Page