MVSFORUMS.com

dhiraj099 · Beginner Joined: 06 Sep 2004 Posts: 2 Topics: 1

It's a cobol-vsam program. Due to change in the copybook in our
re-engineered application, we decided to write a "conversion program"
to translate the copybook of other interfacing applications, within the same environment, into the format of our copybook and re-translate them into the original copybook on the return.

Both the copybooks (Our application and external application) are of the
same length. During translation we do "Move Field1 to Field2", quite
mysteriously the value of last byte of Field2 is not the same as of Field1. Even when we override this with correct value when it's moved to another field once again the last byte is not the same in the receiving field. And it goes on, i.e. every field it touches gets infected and screws the value of the last byte of the target field.

It works fine though with original application (Non-reengineerd one), it
just gets screwed up in translation program during the "Move"
statement. It tried all sortsa fix but didn't work. This is a live project for a major client and we're hopelessly stuck here. Any meeningful help will be sincerely appreciated.

kolusu · Posted: Mon Sep 06, 2004 7:13 am Post subject:

Dhiraj,

Can you post the move statement and the fields associated with it?

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

dhiraj099 · Beginner Joined: 06 Sep 2004 Posts: 2 Topics: 1

MOVE ORD-FBSI-ORD-NUMBER TO CF-ORD-FBSI-ORD-NUMBER. So if ORD- field has a value of "04250BBBBR", at the end of the Move the values stored in CF-ORD is something like "04250BBBB7". The last byte always gets screwed up. I also checked other fields in the vicinity to make sure no overlapping of values from nearby fields. Also no redefinitions occurs here.

When I checked the "Hex" values of these, it's very interesting, for instance the last byte in the Hex strings is always, for instance, D7 in ORD- field but the same is changed to F7 in the CF-ORD- field.

warp5 · Posted: Mon Sep 06, 2004 8:31 am Post subject:

You need to post your definitions, sounds like the one field is defined as numeric signed.

anjanreddy · Beginner Joined: 13 Aug 2004 Posts: 3 Topics: 2

u need to give the two declarations as well the move stmt. then we can try. becoz i am not gettting where exactly the problem is Razz

Mike Chantrey · Posted: Wed Sep 08, 2004 6:03 am Post subject:

As warp5 says, you must surely have it defined as a numeric field and the move is treating the last byte as if it had a sign in it. COBOL MOVE may do sign manipulation depending on the compiler options.

Although these fields are misleadingly called xxxxxxxORD-NUMBER they are clearly not numbers and both the sending and recieving fields should be PIC X(nn).

Mike Chantrey · Posted: Wed Sep 08, 2004 6:07 am Post subject: