| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| using timestamps in TDS format messages |
« View previous topic :: View next topic » |
| Author |
Message
|
| SpitFire |
 Posted: Wed Jan 18, 2006 12:03 am Post subject: using timestamps in TDS format messages |
 |
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
Hi all,
In one of my flows (designed in WBIMB V5.0), I have an element of type 'xsd:datetime'. The full details of the message structure is as follows.
| Code: |
--------------------------------------------------------------
order
orderTime ==> (xsd:datetime,
Tag: TS,
Data Pattern: yyy-MM-dd-HH.mm.ss.SSSSSS,
length: 26,
physical type: characters,
justification: left justify,
padding character: '0')
--------------------------------------------------------------
|
Now in the input when I specify a timestamp value '2006-01-18-12.00.00.123456', it gets interpreted wrongly, and comes out something like this '2006-01-18-12.02.03.456'.
Is this because the accuracy supported is only till the 1000th millisecond? I have to actually enter the value into a database where the support is for 6 digits in the milliseconds place. How do I accomplish this?
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Wed Jan 18, 2006 1:09 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi _z33,
I tried a search on the Broker Help and found this
| Quote: |
| On output from a message flow, the dateTime is always expressed in the fullest form yyyy-MM-dd'T'HH:mm:ss.SSS |
So I guess it is limited to SSS in the output.
You could simply take this value as string and do a CAST AS TIMESTAMP in ur ESQL, if it does not throw an exception means that the value is validated and then you could insert it to the table.
Regards. |
|
| Back to top |
|
|
| SpitFire |
| Posted: Wed Jan 18, 2006 1:26 am Post subject: Limited precision |
|
|
Acolyte
Joined: 01 Aug 2005
Posts: 59
Location: India
|
Hi elvis_gn,
Thanks for the pointer. I think I will have to settle down with the timestamp precision limited to just three digits for the millisecond field. Otherwise I think I have to use String and do a cast on it.
_________________
...: 5|71+ph1|23 :... |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
