|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
Coalesce function rounding error |
« View previous topic :: View next topic » |
Author |
Message
|
koobz |
Posted: Wed Mar 27, 2013 8:52 am Post subject: |
|
|
Novice
Joined: 26 Mar 2013 Posts: 11
|
sent another 10 messages
10 rows appearing in the database, 2 with a rounding error:
Code: |
transactionId RegularHrs
53073500005.000_4 1.95
53073500005.000_4 1.95
53073500005.000_4 1.95
53073500005.000_4 1.95
53073500005.000_4 1.95
53073500005.000_4 1.95
53073500005.000_4 1
53073500005.000_4 1.95
53073500005.000_4 1
53073500005.000_4 1.95
|
logs only show 8 insert statements e.g.
Code: |
2013-03-27 16:29:24.339817 25736 UserTrace BIP2544I: Node 'LabourTransactionToDB.IN_LABTRANS': Executing database SQL statement ''INSERT INTO LABTRANS(transactionId, REGULARHRS...
expressions ''messageId || '_' || CAST(I AS CHARACTER), COALESCE(inRef.XXX1NS:RegularHours, 0.00)...
resulting parameter values '''53073500005.000_4', 1.95...
|
|
|
Back to top |
|
 |
koobz |
Posted: Wed Mar 27, 2013 9:19 am Post subject: |
|
|
Novice
Joined: 26 Mar 2013 Posts: 11
|
scrap that!
the old code was running under a different process...
apparently after deploying using the message broker toolkit GUI, it doesn't always remove the old dataflowengine process.
so as long as only coalesce( X, 0.00) us used it rounds OK.
but I guess that still doesn't explain why putting in the empty tag in the first message guarantees success even with coalescse (x, 0) for later iterations in the while loop. if that makes sense... |
|
Back to top |
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|