decimal zone for informix c-isam

Posted October 1st, 2008 by jch

Hello,
we are problem with decimal zone for informix C-isam.
display "" or amount with decimal=000
example: decimal(15,3)
we take length of zone =9, decimal=3
what's the problem?
urgent.
are you a phone in France?
Thanks

‹ c-tree plus RMCobol indexed file parse questions!!! Urgent help needed ›

RE: decimal zone for informix c-isam

On October 1st, 2008 jterrell said:

Hi jch,

Of the datatype properties that are available for Zoned Decimal, the following are the most important.

Precision
Size
Signed
Sign Pos
Sign Style
Scale
Decimals

When you mark the size of the field in the manual record parser, the Precision and Size properties are filled in automatically. However, you may need to change the default values for the Signed, Sign Position, Sign Style, Scale, and Decimals properties. In particular, the Sign Style setting may need to be changed to reflect the system from which the C-ISAM data originated.

Defining any type of binary, ISAM, or similar data often requires some "trial and error" adjustments before you get all the datatype properties set exactly right for each data field in your file.

Please let us know if you need further assistance.

- Jo

decimal zone for informix c-isam

On October 2nd, 2008 jch said:

hello,
the definition from informix schéma is decimal(15,3).
In parser I put decimal, size=9, decimal=3
the precision is not present
result:
cas 1 : champ=c12300000000000000 in parser=35.000
cas 2: champ=c10714000000000000 in parser=null
cas 3: champ=c20100000000000000 in parser=100.000

if I put in zoned decimal and decimals=3,scale=0, whatever sign pos and sign style:
precision is 9 instead 15 and result=.000
I do not understand ;-(
can send you a file for test?
Thanks

RE: decimal zone for informix c-isam

On October 15th, 2008 jterrell said:

Hi jch,

After looking at your sample data file and the description of the schema, I believe that they are not a "match". In other words, when I manually parsed your C-ISAM file according to the schema description, there are fewer bytes per record than specified in the description.

Please check to see if you have a different schema description that is a better match for the sample data file you sent, and send it to me at your convenience.

- Jo