× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2009

Re: cpyfrmimpf; zone decimal and *fixed

Jimmy Green wrote:
I am trying to use CPYFRMIMPF, it works great except
for fields that are defined as zone decimal

Example of DDS field in the "to file"
FIELD 00007S02 ALIAS(TST_FIELD)

The Field Definition file is as follows
-Fldname-- beg end nul
FIELD 1 7 0

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

After the CPYFRMIMPF the "to file" has 1234500

How can I fix this???


What needs to be fixed? The noted data as physical storage in the "to file", either as the character string "1234500" or the hex string x'F1F2F3F4F5F0F0', is the correct value for any variation of 12345 as zoned decimal data defined as S(7,#) [or as in DDS: 07S0#] where #<=7. That data in physical storage could represent, depending on the scale & precision defined for the numeric field, any of the values:
.1234500, 1.234500, 12.34500, 123.4500, 1324.500, 12345.00, 123450.0, or 1234500.

Regards, Chuck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.