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

S0C7 abend in data movement


IBM Mainframe Forums -> COBOL Programming
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
i_at_forum

New User


Joined: 29 Dec 2005
Posts: 10

PostPosted: Fri Dec 21, 2007 1:58 pm
Reply with quote

Hi,
I have a code which involves data movement from S9(3)COMP-3 to S9(5)COMP-3 field. It is giving S0C7 abend. Changed the receiving field to S9(3)COMP-3 the problem got solved.
Can any one tell what is the reason.
Back to top
View user's profile Send private message
murmohk1

Senior Member


Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India

PostPosted: Fri Dec 21, 2007 2:05 pm
Reply with quote

i_at_forum,

Relevant topic discussed earlier. Link below-

www.ibmmainframes.com/viewtopic.php?t=3155&highlight=s0c7
Back to top
View user's profile Send private message
socker_dad

Active User


Joined: 05 Dec 2006
Posts: 177
Location: Seattle, WA

PostPosted: Wed Dec 26, 2007 9:28 pm
Reply with quote

Of course it is possible to go from a smaller numeric field to a larger numeric field: the extra bytes are zero-filled. That is, numeric fields have zeroes in the high-order places:

Sending: 995V99

Receiving: 00995V99

However, I am completely confused as to getting a 0C7 on this move. It seems impossible to me, given that the sending field is valid numeric. Can someone explain this in more detail?
Back to top
View user's profile Send private message
Phrzby Phil

Senior Member


Joined: 31 Oct 2006
Posts: 1042
Location: Richmond, Virginia

PostPosted: Thu Dec 27, 2007 3:07 am
Reply with quote

That is - can we see the data in hex please, preferable a screen print.
Back to top
View user's profile Send private message
Max Payne

New User


Joined: 13 Dec 2007
Posts: 10
Location: Shanghai

PostPosted: Fri Jan 04, 2008 9:50 am
Reply with quote

First, we need the Hexcode of the field of S9(3) COMP-3.
Second, without detail information, we can only suggest that you check whether another field (like type X) has redefined your S9(3) comp-3
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Fri Jan 04, 2008 1:01 pm
Reply with quote

Yup that's a valid MOVE. I would repeat
Quote:
we need the Hexcode of the field of S9(3) COMP-3.
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 -> COBOL Programming

 


Similar Topics
Topic Forum Replies
No new posts Data set Rec-Cnt and Byte-Cnt Testing & Performance 2
No new posts ISAM and abend S03B JCL & VSAM 9
No new posts SCOPE PENDING option -check data DB2 2
No new posts Check data with Exception Table DB2 0
No new posts JCL EXEC PARM data in C Java & MQSeries 2
Search our Forums:

Back to Top