Daylight Saving Time Help and Support Center
Additional Resources http://www.sia.com/business_continuity/html/dst.html
The U.S. Energy Policy Act of 2005, passed by the U.S. Congress July, 2005, extended Daylight Saving Time (DST) in the U.S. by approximately four weeks. As a result, beginning in 2007, DST will start three weeks earlier on March 11, 2007, and end one week later on November 4, 2007, resulting in a new DST period that is four weeks longer than previously observed. These for weeks are referred to in this article as the “extended DST period”. Visit MSN Encarta for more general information on DST.
Previously DST started on: With the new law, DST will start on:
First Sunday of April (04/01/07) Second Sunday of March (03/11/07)
Previous DST ended on: With the new law, DST will end on:
Last Sunday of October (10/28/07) First Sunday of November 11/04/07
Unless certain updates are applied to your computer, it is possible that the time zone settings for your computer’s system clock may be incorrect during this four week period. This depends on where you live and which time zone you have selected. To see the time zone settings on your computer, follow these directions.
When your time zone settings are incorrect your clock may be off by one hour, and certain applications running on your Windows based computer may not display the correct time. To address this, Microsoft is providing many free updates and tools that will update your system automatically.
Top Issues
Microsoft products affected by 2007 daylight saving time changes
What end users can do to ease the transition
General sequence of update actions and special considerations
Supporting the DST changes on Windows operating systems
Preparing other Microsoft software products for the 2007 DST changes
Daylight Savings Time (DST) – IT Resource center
Typically, on the first Sunday in April, most computer systems, software and applications automatically switch over to DST. However, due to a 2005 federal energy conservation initiative, 2007 will mark the first year in which DST will begin three weeks earlier (March 11th) and end one week later (November 4th) than previous years. Many IT system components were developed previous to this change, and therefore will require patches, upgrades, or in some cases, manual updates, in order to reflect DST. This year, all action required in order to ensure a seamless crossover will need to be completed by March 10th. For the securities industry, making these upgrades and changes as quickly and efficiently as possible is critical in order to assure there are no disruptions to the global financial markets.
Please continue to check back with this site for updated information. We will also be planning conference calls for members to learn more about these issues, how their firms might be impacted, and how they can best prepare.
To learn more about SIFMA member firm experiences please click here.
Frequently Asked Questions
How will DST affect our systems?
How do we know which systems, software and applications are in need of patches and which will automatically update?
Are there resources available to help me plan?
DST Checklist – 5 Tips
If you have not yet prepared for DST, below are a few tips to help you start preparing for DST.
Create a checklist of hardware, software, applications and other IT systems vendors used by your organization. Be in contact with each one to get the most up-to-date information. Keep a running list so that you’ll know which items are taken care of and which you’ll need to manually update.
Notify your staff of the DST issue, so that they will be prepared for any minor glitches that might occur on March 11th.
Remember the DST end date, November 4th, so that you are properly preparing your system to handle the start as well as the end of DST.
Test your system in advance of March 10th so you know in advance which glitches you might face, and which you can solve before the DST change.
Work with your firm to create contingency plans in the event that any disruptions might occur.
Gartner recently issued DST implementations, they include the following: NEW
After applying patches or manual fixes, conduct tests to verify that the proper times and dates are produced.
Review all applications and their interactions with other applications for DST change compliance.
Check with external service providers to ensure that they are modifying their own systems to comply with the changes so your systems are not negatively affected.
Have IT personnel scheduled to be available during the DST change on March 11 so they can repair any problems that arise, and give them well-defined escalation procedures to deal with any circumstances.
IT departments should schedule twice-yearly reviews prior to DST shifts to confirm that systems are working smoothly and to correct any problems that occur.
What to Watch Out For
While there are many areas of your IT system that need to be reviewed, some issues to pay close attention to include:
Batch processes
Backup windows
Time stamps when trade books are hand-over between geographic locations
Messaging systems time stamps and workflow
Applications using hard coded calendars
Global applications outside of the US which US users use
Helpful Resources
Below please find links to useful information centers; patches for updates; other support services:
Avaya:
http://support.avaya.com/japple/css/japple?PAGE=OpenPage&temp.template.name=DLT2007
BEA Systems:
http://support.bea.com//support_news/Patch_for_2007_Daylight_Savings_Time_Changes.jsp
Bluecoat
http://www.bluecoat.com/support/self-service/6/dst2k7.html
Country list:
http://www.timeanddate.com/time/dst2007a.html
Hewlett-Packard:
http://h71000.www7.hp.com/dst.html
HP Java
http://www.hp.com/products1/unix/java/DST-US.html
IBM:
http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FQ115943
Informix
http://www-1.ibm.com/support/docview.wss?rs=630&context=SSGU8G&context=SSHPYE&dc=D600&uid=swg21248851&loc=en_US&cs=UTF-8&lang=en
Java:
http://java.sun.com/developer/technicalArticles/Intl/USDST/
Linux:
http://packages.debian.org/unstable/libs/tzdata
Lotus Notes:
http://www-1.ibm.com/support/docview.wss?uid=swg21245334
Microsoft:
http://www.microsoft.com/windows/timezone/DST2007.mspx
PeopleSoft:
http://peoplesoftexperts.blogspot.com/2006/10/impact-of-us-daylight-saving-time.html
Red Hat 2.1
http://rhn.redhat.com/errata/RHEA-2006-0208.html
Red Hat 3.0
http://rhn.redhat.com/errata/RHEA-2005-655.html
Sun:
http://www.sun.com/bigadmin/features/techtips/dst_changes.html
SUN O.S.
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102178-1
http://sunsolve.sun.com/search/document.do?assetkey=1-26-102617-1
Sybase
http://www.sybase.com/detail?id=1048699
Apple OSX:
http://docs.info.apple.com/article.html?artnum=303411
Blackberry:
There will be a server side patch for Blackberry Enterprise Server. Some older Blackberry models will also need a firmware patch.
http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/1292899/Impact_of_North_American_Daylight_Saving_Time_
changes_in_2007_on_BlackBerry_customers.pdf?nodeid=1293007&vernum=0
http://www.blackberry.com/select/dst2007/index.shtml
Cisco:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00807ca437.shtml
Informix:
Lotus Notes stores the timezone in a meeting record and therefore needs every meeting created during the affected intervals to be changed. IBM has developed a response to this issue. It can be at: found at: http://www-1.ibm.com/support/docview.wss?uid=swg21247972
Microsoft:
The key thing being emphasized was the timing of the patch installations. This is echoed in the article below, which is the best and clearest summary of the MS recommended approach for the DST patches. Another important point of emphasis from the article is the fact that the group of patches need to be installed as closely together as possible as odd results can occur while only some of the required group of patches has been installed.
ZipLip is a product that could be especially susceptible to patch overlap. Also note that the client Outlook update tool is interactive and requires input from the user to operate at it best. How this will work for Citrix clients is unclear.
Note: silent switch available on the Outlook client tool that may not handle all scenarios correctly. There are a few affected products on the list that I would not have expected to see there including Sharepoint 2.0 and SourceSafe.
http://www.microsoft.com/windows/timezone/dst2007.mspx
Oracle:
http://blogs.oracle.com/schan/2006/11/29#a988
Changes to Daylight Saving Time (DST) in 2007 in the US, Canada and Bermuda will affect the display and calculation of dates and times for Lotus Notes and Domino. To assist you with implementing changes to your systems, communicating the changes throughout your organization, and understanding more of the details, the following updated information is now available:
Title: Executive Summary and End User Guide: Daylight Saving Time (DST) 2007
URL: http://www.ibm.com/support/docview.wss?rs=463&uid=swg21254625
Content: Information to help IT System Administrators and Help Desk personnel communicate the changes for DST within you organization.
Title: Deployment Guide: Daylight Saving Time (DST) 2007
URL: http://www.ibm.com/support/docview.wss?rs=463&uid=swg21254624
Content: Step-by-step instructions to implement the changes needed to prepare your Lotus Notes and Domino systems for the DST 2007 changes, along with Frequently Asked Questions.
Title: Agents for updating Calendaring and Scheduling entries and Resource Reservation entries for Daylight Saving Time (DST) 2007
URL: http://www.ibm.com/support/docview.wss?rs=463&uid=swg21254639
Content: The released agents, instructions for applying the agents, and a detailed description of how the agents work.
Complete information about addressing Changes to Daylight Saving Time (DST) in 2007 for Lotus Notes and Domino can be found on http://www.ibm.com/support/docview.wss?rs=463&uid=swg21247972. Additional notifications will be sent when new information is available.
Pivotal:
Pivotal claims that they will not be affected. The product itself may not be affected but OSM/Intellisync needs special attention which, IMO, has not been given to this point by Pivotal support.
RedHat Linux:
http://rhn.redhat.com/errata/RHEA-2005-656.html
Solaris:
http://www.sun.com/bigadmin/features/techtips/solaris_dst_addendum.jsp
SUN JRE:
All Desktop JRE versions below a specified version will need to be updated (preferable) or will need a special DST patch from Sun. More info here:
http://java.sun.com/developer/technicalArticles/Intl/USDST/
SuSE:
Tandem:
http://www.itug.org/forums/forum/messageview.cfm?catid=89&threadid=2725&enterthread=y