The beginning of this important information about Daylight Saving Time has been provided by Brian Coles as part of his valuable information about AIX which I’ve placed in another article. The important point right now is:
At 2am on Sunday October 29th, 2006, set your clocks back one hour if you’re in DST. But that’s not all !
United States 2006 Daylight Saving Time officially finishes on this coming Sunday October 29th at 2:00AM. After this Sunday, all future Daylight Saving Time periods require changes to be applied for the start and stop times by virtue of the Energy Policy Act of 2005 (Public Law 109-58) which was passed by the United States Congress on July 29, 2005 and signed into law on August 8, 2005.
Previously, and currently in 2006, US DST always began on the first Sunday of April at 2:00AM and ended on the last Sunday in October at 2:00AM. Beginning in 2007, US DST will begin on the second Sunday of March at 2:00AM and end on the first Sunday of November at 2:00AM. These important changes need to be applied to ALL of your systems so that they will manage the DST changes automatically and correctly in future, at the appropriate new dates and times.
Get a time jump on US DST 2007 and its changes, be proactive now and check it and set it early rather than late, or even too late ! As in those famous tv commercials, Ron says ~ "Set it and forget it !"
To avoid any particular problems with the current operating US DST 2006 period and settings, it is suggested that any corrections to the US DST 2007 period should not be applied until AFTER November 05, 2006 and BEFORE March 11, 2007. However, the sooner corrections are applied the better, so they are not to be forgotten and applied too late ! Please be proactive !
Brian Coles is an AIX Engineer, and provides professional consulting and development services.
The changes to DST in 2007 will affect our computer software in different ways. Software older than just a few months may not be prepared for the changes. Yes, this is starting to sound like Y2K all over again, but this will affect far fewer environments and, depending on the environment, much less drastically.
For AIX issues and solutions, I’ve posted an article by Brian. For other environments I will post information in the Time category as it comes available. Please feel free to contribute content, offer services, or request consultation, and we’ll try our best to partner people with information and solution providers. Information is welcome regarding how other environments will be handling the changes discussed here.
Nebula Research and Development will provide "Research" and yes, "Development" services, to investigate sites and software to help determine and eliminate vulnerabilities.
Notes are welcome regarding MV DBMS vulnerabilities and MV application code issues. More will be posted here … as time permits…
Statements in this article which were obtained from other sources have not been verified. Neither Nebula Research and Development, nor Tony Gravagno are responsible for the use or interpretation of information, software, or any other material obtained in these articles or from sites not under our control.