View previous topic :: View next topic
|
Author |
Message |
i_at_forum
New User
Joined: 29 Dec 2005 Posts: 10
|
|
|
|
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 |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006 Posts: 1436 Location: Bangalore,India
|
|
Back to top |
|
|
socker_dad
Active User
Joined: 05 Dec 2006 Posts: 177 Location: Seattle, WA
|
|
|
|
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 |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006 Posts: 1042 Location: Richmond, Virginia
|
|
|
|
That is - can we see the data in hex please, preferable a screen print. |
|
Back to top |
|
|
Max Payne
New User
Joined: 13 Dec 2007 Posts: 10 Location: Shanghai
|
|
|
|
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 |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
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 |
|
|
|