IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

S0C7 Data Exception Error


IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Niti Srivastava

New User


Joined: 15 Feb 2015
Posts: 1
Location: India

PostPosted: Mon Feb 23, 2015 5:40 pm
Reply with quote

Hi,

M getting following error :
Spool Details are :
Code:
cd-co: 0012
HJ23-CU0575A-KEY-GRP:
LJ23-CU0575A-KEY-GRP:
TABLE-MAX: IN 9300-000{
TABLE-MAX: IN 9300-000A
CEE3207S The system detected a data exception (System Completion Code=0C7).
         From compile unit CURP8703 at entry point CURP8703 at compile unit offset +000031BA at entry offset +000031BA at address 21403F5A.


I am unable to find out where is it throwing the S0C7 error.
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA

PostPosted: Mon Feb 23, 2015 6:25 pm
Reply with quote

What is the PICTURE clause of "TABLE-MAX"?
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Mon Feb 23, 2015 7:00 pm
Reply with quote

Quote:
I am unable to find out where is it throwing the SOC7 error.
Unlike C and Java and other such languages, COBOL (like most mainframe languages) does NOT "throw errors" -- it generates ABENDS. Terminology is critical in IT where similar terms may mean very different things -- and you need to learn mainframe terminology.

Second, the system tells you the offset in the program where the ABEND occurred -- a compile of the program will give you the offsets for each statement, and as long as you can compare hexadecimal values you can figure out which COBOL statement includes offset 31BA. So there is no reason you would be unable to find out where the ABEND is occurring. Figuring out why the ABEND occurred may be more difficult but certainly not impossible.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 3048
Location: NYC,USA

PostPosted: Fri Feb 27, 2015 7:07 am
Reply with quote

Welcome!!

Please add sufficient display to get close to problem or quicker way as Robert suggested please look into compile listing and search for 31BA ro get the like number.
Back to top
View user's profile Send private message
don.leahy

Active Member


Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada

PostPosted: Fri Feb 27, 2015 7:25 pm
Reply with quote

Robert Sample wrote:
Quote:
I am unable to find out where is it throwing the SOC7 error.
Unlike C and Java and other such languages, COBOL (like most mainframe languages) does NOT "throw errors" -- it generates ABENDS. Terminology is critical in IT where similar terms may mean very different things -- and you need to learn mainframe terminology.

Agree that Cobol programs on the mainframe do not 'throw' errors. Though if they did they would throw them faster and more reliably than programs running on other platforms. icon_biggrin.gif
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> ABENDS & Debugging

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts Data set Rec-Cnt and Byte-Cnt Testing & Performance 2
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts SCOPE PENDING option -check data DB2 2
Search our Forums:

Back to Top