Data Move ment problem

Debasis Misra · New User Joined: 16 Sep 2008 Posts: 72 Location: Bangalore

A PIC 9(05).
B PIC 9(3).

Case1
-----------
Move A to B

Then, if A = 12345
B = 345
So, my first 2 MSB is truncating.

Case 2
-------------
A temporary variable : C PIC X(3).

Move A to C
Move C to B

Then, if A = 12345
B = 123
Its correct.

But if A = 00009
then B =000

Which is incorrect.
-----------------------
A and C declaration we cant change.

Please help me out.

anandinmainframe · Active User Joined: 31 May 2007 Posts: 171 Location: India

Debasis Misra,
Why dont you declare
B PIC 9(3) as
B PIC 9(5).
if you have a input which can be a 5 Digit number.

dick scherrer · Posted: Fri Apr 10, 2009 9:47 am

Hello,

Debasis Misra · New User Joined: 16 Sep 2008 Posts: 72 Location: Bangalore

Sorry ANAND, its my mistake.

'A and C declaration we cant change' -- wrong
'A and B declaration we cant change' -- correct one.

anandinmainframe · Active User Joined: 31 May 2007 Posts: 171 Location: India

Debasis Misra,

dick scherrer · Posted: Fri Apr 10, 2009 10:21 am

Hello,

Without regard to the specific lines of code and variable definitions, it would be a good idea to show all possible patterns of input that may arrive for processing and what the output should be for each different type of input.

Once the rules are understood by those of us involved with this topic, more useful suggestions will result.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

If you desire 123 in B, try MOVE A(1:) to B(1:).

But, as Dick has hinted, you may be surprised by the results with some A values, e.g. A=12; result of MOVE: B=000.

Robert Sample · Posted: Fri Apr 10, 2009 4:46 pm

You could use EVALUATE to determine which bytes of A to move to B, but as was said earlier this is a bad design -- moving 5 bytes to 3 bytes means something is going to get lost.