| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Time data type behavior |
« View previous topic :: View next topic » |
| Author |
Message
|
| swethabala |
 Posted: Wed Mar 31, 2010 10:26 pm Post subject: Time data type behavior |
 |
|
Apprentice
Joined: 25 Aug 2009
Posts: 44
|
Hi All,
We got a strange problem in our interface. In an outbound interface there is a field called transaction time declared as time data type.
When SAP triggers the data for this interface it is having Transaction time as "17:37" however in WMB the transaction time for the same file is taken as "5:37".
This means WMB is taking 12 hours clock not 24 hours clock. Could you please let me know should we set these properties to make WMB to recieve what ever time comes from SAP?
I tried to check in IBM support center but no clue found.
Thanks
Swetha |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Apr 01, 2010 12:10 pm Post subject: Re: Time data type behavior |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| swethabala wrote: |
Hi All,
We got a strange problem in our interface. In an outbound interface there is a field called transaction time declared as time data type.
When SAP triggers the data for this interface it is having Transaction time as "17:37" however in WMB the transaction time for the same file is taken as "5:37".
This means WMB is taking 12 hours clock not 24 hours clock. Could you please let me know should we set these properties to make WMB to recieve what ever time comes from SAP?
I tried to check in IBM support center but no clue found.
Thanks
Swetha |
I believe this depends on the locale you are using.
Check the time properties and timestamp format definitions.
I'm sure you can get it to pass the time in 24 hours format.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| swethabala |
| Posted: Fri Apr 02, 2010 3:26 am Post subject: |
|
|
Apprentice
Joined: 25 Aug 2009
Posts: 44
|
Thanks for a responce.
The Format in the message set is declared as HH:mm:ssZZZ. The data type is Time.
We are not able to understand why it is taking 12 hour clock. We dont know where to do the setting to get 24 hours clock.
One simple solution for this will be changing the data type to string. We suggested this solution only for now As we are unable to understand the behaviour of Time data type..
But this still remains a question, what are time data type properties? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Apr 02, 2010 5:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There's a vast difference between a) the internal representation of a TIME value, b) the default external representation of a TIME value, c) the external representation of a TIME value produced by a properly built CAST / based on a message definition value
You don't care about a) in the slightest, I promise.
You really shouldn't be using b) if you're concerned about 24 hour vs 12 hour values.
If you're not getting the right value from c) then your pattern is not correct. |
|
| 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
|
|
|
|
