RE: cpyfrmimpf

IF the data in the input file is 0012345 after the cpyfrmimpf it should be
00123.45 but, it's not.
It's changing to 1234500

The cpyfrmimpf is actually moving the first two bytes to the end for the
decimal. Is that the way the cpyfrmimpf is supposed to work?????



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Simon Coulter
Sent: Tuesday, June 09, 2009 6:31 PM
To: Midrange Systems Technical Discussion
Subject: Re: cpyfrmimpf


On 10/06/2009, at 5:57 AM, Jimmy Green wrote:

Example of DDS field in the "to file"

FIELD 00007S02 ALIAS(TST_FIELD)



The Field Definition file is as follows

-Fldnme beg end nul

FIELD 1 7 0



The "from file" (.txt) has the data as 0012345

After the CPYFRMIMPF the "to file" has 1234500

What did you expect to see?

1234500 is the correct value for your data applied to the defined
field. DDS (and therefore the file itself) shows the field as a
ZONED(7,2) which means the field can hold 7 digits, 5 to the left of
the implied decimal point and 2 to the right. Therefore the value in
the field is interpreted as 12345.00 which is correct.


Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------