OneWorld Service Pack SP22 Math Numeric APIs

We are experiencing an issue between our current service pack (SP 16) and
the latest service pack release (SP22). Whilst testing the JD Edwards
applications with Service Pack 22 an unexpected bug was found and the
problem traced to the non-initialisation of a MATH_NUMERIC variable in a C
business function. We have run further tests and found:

Service Pack 16: The non-initialised math numeric field has a MathZeroTest()
result returned of ‘1’.
For the same business function -
Service Pack 22: The non-initialised math numeric field has a MathZeroTest()
result returned of ‘0’.

This result implies that the MathZeroTest() API behaviour has changed
between SP 16 and SP 22. Of most concern is that this change could adversely
effect any OneWorld C programming where a MATH_NUMERIC has been used and not
initialised before calling the API. Applications that would previously
execute the conditional logic where the API call returns TRUE will now be
FALSE and vice versa.

Has anyone come across this issue in Xe U2. The issue seems to be fixed in
later updates as the JDE business functions have been changed to implicitly
initialize the math numeric variables.

Marcelle

Xe U2 SP16 / Unix HP / Oracle

_________________________________________________________________
Use MSN Messenger to send music and pics to your friends
http://www.msn.co.uk/messenge

Marcelle,

I doubt the difference in results you saw in your tests were due to changes in the MathZeroTest api.

Rather, the contents of the variable memory space happened to be different and because the variable wasn't initialized sometimes you'll have x'000000 and sometimes something else. The real bug is the variable not being initialized before being referenced.

No programmer should have assumed a default value of zero (when programming in 'C' anyway). So I don't think this is a major issue.

What do you mean by "U2"? Update 2?

Regards,

Larry,
By U2 I do mean Xe Update 2. Just want to check that this is not a major issue before we move to SP22, and see if anyone has come across this problem with SP21/SP22 on Update 2.