Floating point multiplication rules

niks_jude · Posted: Thu Aug 16, 2007 3:48 pm

I have three fields.
x1 = 00.0010000 PIC S9(2)V9(7) COMP-3.
x2 = 0000.04025 PIC S9(4)V9(5) COMP-3.
x3 = 000100000.00 PIC S9(9)V9(2) COMP-3.

when I muilply these and the result is in comp-2(floating point field), the result is not 4.025E0 but 4.0249999999999999E+00.

Y = x1 * x2 * x3.

I read in the manuals that this is becuase all the fields are converted to floating point. How does this conversion take place? And how is the result justififed. I cannot use any other type field than floating point field.

CICS Guy · Posted: Thu Aug 16, 2007 4:01 pm

The primary problem is the total number of digist possible, your numbers are exceeding some limit the compiler uses in decieding how to do the calculation.
Floating point has a larger range but you may need to half round the result.
If x3 is always that large, pre calculating x1 * x3 and then multplying x2 to the intermediat total might keep everything decimal.....

agkshirsagar · Posted: Thu Aug 16, 2007 4:09 pm

Do you have any problem with the result?
The difference between two result is insignificant (1 * 10^-16). Unless you are doing scientific work the result should be OK for you.
I will suggest not going to the details of conversion because it is quite different from standard IEEE 754 and difficult to follow (Atleast to me).

William Thompson · Posted: Thu Aug 16, 2007 4:20 pm

niks_jude · Posted: Thu Aug 16, 2007 9:14 pm

I cannot try with x3 = x1 * x3
and y = x3 * x2.
because it may lead to truncation in extreme conditions.

Do I have any other option.

Because its a production problem, In cannot change the compiler option also.

CICS Guy · Posted: Thu Aug 16, 2007 9:31 pm

niks_jude · Posted: Thu Aug 16, 2007 9:35 pm

This would require the production compiler options to be chnaged which is not feasible. As other elements may get out of synch.

Is it possible to do this with tricky use of intermediate variables?

dbzTHEdinosauer · Posted: Thu Aug 16, 2007 9:45 pm

I believe that you can include Compiler Options in the source. That would remove the 'special' compiliation circumstances.

Not knowing what kind of application is in use hinders 'work around solutions'. I have worked for banks and transportation companies - neither of which ever required floating point. So, I can't (should not) make any rash judgements or decisions....... but, why is their only one module in the company that requires this kind of arithmetics?

CICS Guy · Posted: Thu Aug 16, 2007 9:48 pm

niks_jude · Posted: Thu Aug 16, 2007 11:28 pm

Thanks I would have to ask the senior guys if this is allowed in our production environmenr.

dick scherrer · Posted: Fri Aug 17, 2007 1:05 am

Hello,

niks_jude · Posted: Fri Aug 17, 2007 10:12 am

No the requirement is following ---------

Use floating point till last step. In the last step round the floating point result to two decimal places.

William Thompson · Posted: Fri Aug 17, 2007 1:55 pm

niks_jude · Posted: Fri Aug 17, 2007 2:38 pm

Yes. I thought of using some intemediate flaoting variables so that the dip in value is not there.

William Thompson · Posted: Fri Aug 17, 2007 2:45 pm

Won't help, just half round and be done with it.....

dick scherrer · Posted: Fri Aug 17, 2007 8:33 pm

Hello,

Please explain the requirement that restricts the process to floating point. I do not understand such a requirement for what it appears you need to accomplish.

What business reason dictates this? If there is no business reason, using standard arithmetic would be a better choice.

niks_jude · Posted: Sat Aug 18, 2007 11:52 am

We have been provided this in design specifications and we have to abide by it. Even I cannot really understand the requirement but I have to strictly follow the design specifications. Thanks.