| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ time discrepancy |
« View previous topic :: View next topic » |
| Author |
Message
|
| tleichen |
 Posted: Thu Mar 13, 2008 10:12 am Post subject: MQ time discrepancy |
 |
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
We have servers that have no access to the internet and thus have no connectivity to an SNTP. This appears to throw off many of MQ's times, as the system winds up using local time for GMT, and sometimes uses the local timezone to bias off of that time. From where we are located, that throws the times off five or six hours, depending on the time of year. Is there any solution that can compensate for this? 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 13, 2008 10:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's your system that's configured wrong, if MQ is confusing GMT with local time by an amount that is presumably the same as your GMT Offset.
I.e. your system administrators have set the machine to be in the GMT timezone, and then tweaked the clock to match the local time.
What should have been done is setting the machine to be in the local timezone and allowing the OS to handle the GMT Offset and making a note to manually update the clock twice a year at least.
Access to an SNTP only ensures that the clock is reasonably accurate at any given time - it does nothing to ensure that the OS thinks the machine is in the correct timezone!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Mar 13, 2008 7:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| jefflowrey wrote: |
It's your system that's configured wrong, if MQ is confusing GMT with local time by an amount that is presumably the same as your GMT Offset.
I.e. your system administrators have set the machine to be in the GMT timezone, and then tweaked the clock to match the local time.
What should have been done is setting the machine to be in the local timezone and allowing the OS to handle the GMT Offset and making a note to manually update the clock twice a year at least.
Access to an SNTP only ensures that the clock is reasonably accurate at any given time - it does nothing to ensure that the OS thinks the machine is in the correct timezone! |
No but if the machine thinks it's GMT the sntp server would set it to the GMT time... preventing the admins from doing the trick... of changing the time to make it look local...
If you don't have access to the Internet from those machines you need to set up your own sntp server and connect them to it. So you can have a server that is connected to the Internet and acts internally as time coordinator for the parts of your network that cannot connect to the Internet.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon Mar 17, 2008 8:23 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
Well, that certainly would make more sense. Why it is not set up that way, I'm still trying to find out. 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| 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
|
|
|
|
