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

S0C7 While calling a program


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

New User


Joined: 09 Jan 2008
Posts: 4
Location: Baskingridge

PostPosted: Fri May 28, 2010 4:43 am
Reply with quote

I m getting S0C7 when calling a program.

CALL 'ABCD' USING A-XYZ B-XYZ.---> In this line getting S0C7

Can somebody tell me what might be causing this.
I have verified the linkage data and everything is valued correctly.
Also If I run the same Job thru expeditor I m not getting S0C7 abend. job runs successfully.
Back to top
View user's profile Send private message
CICS Guy

Senior Member


Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table

PostPosted: Fri May 28, 2010 5:22 am
Reply with quote

dilipsvd wrote:
I m getting S0C7 when calling a program.
CALL 'ABCD' USING A-XYZ B-XYZ.---> In this line getting S0C7
Can somebody tell me what might be causing this.
Bad data.....
Quote:
I have verified the linkage data and everything is valued correctly.
And how did you 'verify' this?
Quote:
Also If I run the same Job thru expeditor I m not getting S0C7 abend. job runs successfully.
Curious.....
Back to top
View user's profile Send private message
dilipsvd

New User


Joined: 09 Jan 2008
Posts: 4
Location: Baskingridge

PostPosted: Fri May 28, 2010 5:42 am
Reply with quote

1) Verified data using Display (COMP3 were moved to numeric and so on)
2) and in expeditor

My understanding was, even if there is bad data in the linkage it should not cause problem until it is used in the calling program
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Fri May 28, 2010 5:58 am
Reply with quote

Hello,

Quote:
My understanding was, even if there is bad data in the linkage it should not cause problem until it is used in the calling program
Either your understanding is incorrect or this is a typo. . .

If a field is defined as comp-3 and does not have valid numeric data, it can cause a s0c7 in either the calling or the called module. . . Suggest you find what value is in the field when the 0c7 happens.

One reason that the run might run ok under xpediter is that some of the values are at different places in memory than when not run with Xpediter and sometimes there is a valid numeric value and other times not. Suggest looking for an uninitialized variable. A good practice is to move zeros (or some other value) to all comp-3 fields (either as a VALUE, an INITIALIZE, or a MOVE).
Back to top
View user's profile Send private message
CICS Guy

Senior Member


Joined: 18 Jul 2007
Posts: 2146
Location: At my coffee table

PostPosted: Fri May 28, 2010 6:26 am
Reply with quote

dilipsvd wrote:
CALL 'ABCD' USING A-XYZ B-XYZ.---> In this line getting S0C7
What proof is it 'this line' that is causing the S0C7? And don't give me that 'expeditor' crap, look at the dump, all the answers are there.
Are you sure that it is not a S0C4?
Where does the PSW point to? What is the assembler code at that (always provided) PSW?
CALLs do not S0C7, they might S0C4 or others, but S0C7 requires an assembler instruction that is interruptible by a 'data exception'.....
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 Using API Gateway from CICS program CICS 0
No new posts Calling DFSORT from Cobol, using OUTF... DFSORT/ICETOOL 5
No new posts Calling Java method from batch COBOL ... COBOL Programming 5
No new posts Calling an Open C library function in... CICS 1
No new posts DB2 Event passed to the Application P... DB2 1
Search our Forums:

Back to Top