Kelly Bert Manning wrote:
There has been a lot of buzz recently about DST starting on a different
day in some jurisdictions.
Most of the concern was about failing to make the change at the mandated
time and having interval or sequence computation fail as a result.
Our Service Bureau has a habit of changing the time 3 hours late, at the
time of their usual weekly outage window.
I'm concerned that leaves a 3 hour gap during which it could be 1 hour
behind servers and end users who have already had their workstations and
office clocks reset to DST.
How common is it it do delay DST changes and simply run out of sync with
the rest ouf your state/province, etc. for several hours?
When MVS was interacting with fixed function "Green Screens" this obviously
wasn't a big deal. Now that it is interacting with multi tier applications
and web users accessing at all hours of the day and night it seems like
time to get with the DST program and avoid having a clock which is out of
sync with everyone else in the same jurisdiction.
My personal opinion, if time is that critical then you should be using
UTC/GMT time for anything that requires the time to be in sync.
What happens if the person/server is not even in your time zone?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
