Guidance on updating Java SDKs and JREs for Daylight Saving Time (DST) changes

How do DST changes affect my system?
When do I need to update my system?
I need to update straight away. What must I do?
How do I validate DST changes?

---

How do DST changes affect my system?

Java applications that are sensitive to time and date information will require updating to ensure that all relevant time and date calculations are correct. Many IBM products contain Java technology and are affected by these changes.

---

When do I need to update my system?

The latest DST information is included in new product service refreshes and your systems will be updated as part of your planned maintenance schedule. You need to update your systems ahead of this schedule only if you are affected by recent DST changes.

Consider the following:

• Do you run Java applications that perform time and date processing?
• Is it important for your applications to function correctly on the affected dates? Consider the risks to your business and your customers business if your applications calculate time incorrectly.
• Are the countries significant to your business changing their DST?
• Does your system already contain DST updates for the countries significant to your business?

To see which time zone updates are included in Java SDK or JRE service refreshes, see Olson time zone updates for Java JRE and SDK service refreshes for IBM products.

To search for SDKs and JREs on your system and see the current update level, see How do I validate DST changes?

---

I need to update straight away. What must I do?

For your Java applications to work correctly with the new DST updates, you must update both your operating system and your Java SDK and JRE. Java relies on the operating system to provide an accurate clock and it relies on locale information to indicate the active time zone. Inaccurate settings will cause Java to represent time incorrectly.

For your Java applications to work correctly with the new DST updates, you must update both your operating system and your Java SDK and JRE.

Updating your operating system

The update process you must follow depends on your operating system.

• IBM AIX, z/OS, IBM i, Linux on IBM hardware, VIOS. See IBM Support and Downloads.
• Red Hat Linux: Use normal update procedures.
• Novell SUSE Linux. Use normal update procedures.
• Sun Solaris: See Sun Solaris Support.
• HP HP-UX: See HP Support.
• Microsoft Windows: See Microsoft Support. Note: Use a Microsoft patch or the tzedit.exe utility to update your Microsoft Windows system. See Java Daylight Saving Time: Known problems and workarounds for more information.
• Other operating systems: Contact your vendor.

Updating your Java SDKs and JREs

You might have more than one SDK or JRE on your system that needs updating. Follow these steps until you find a suitable update method for each SDK or JRE.

1.	Java on IBM i See Updating Java for Daylight Time Saving changes on IBM i platforms.
2.	Java embedded in an IBM product, including JDKs supplied by IBM for products on Solaris or HP-UX. Consult the product support pages. Where possible, use a product specific patch to update your SDK or JRE.
3.	Java provided with your operating system For Java on AIX and z/OS, see the support pages for your operating system. For other platforms, follow the instructions in the next step.
4.	Java installed separately If your SDK or JRE was downloaded from IBM DeveloperWorks or supplied by a Linux distributor, install the latest Java service refresh. For information about the level of Java required, see Olson time zone updates for Java JRE and SDK service refreshes for IBM products. You can download Java from developerWorks.
5.	If IBM product service or a Java service refresh is not yet available for the country updates you need, or If you are using the IBM 32-bit Runtime Environment for Java 2 (JRE) Windows Edition on IBM Personal Computing products manufactured prior to 1 Apr 2005, or If you are using the IBM Development Package for Eclipse. Use the IBM Time Zone Update utility for Java (JTZU), which applies the latest time zone update information directly to IBM Java SDKs and JREs. For more information and to download JTZU, see IBM Time Zone Update Utility for Java Download Page .
6.	If you are using an obsolete version of Java Upgrade to a supported level of the IBM product or the Java SDK or JRE.

Deciding between applying service and using JTZU

Update your IBM SDK or JRE by applying a Java Service Refresh, Fix Pack or interim fix. However, there are some situations when this might not be possible, for example:

• You require DST updates for countries not yet covered by the Service Refresh, Fix Pack, or interim fix.
• You require DST updates ahead of your maintenance schedule and cannot bring the schedule forward.
• You have applied an interim fix for an essential "custom" service and you want to avoid reverting the interim fix.

In these circumstances you can use JTZU to update your IBM SDK or JRE.

Note: JTZU does not support Java on IBM i platforms. To apply Daylight Saving Time changes to Java on IBM i systems, see Updating Java for Daylight Time Saving changes on IBM i platforms.

---

How do I validate DST changes?

After updating your system, you can validate the changes to a Java SDK or JRE by using JTZU.

Using JTZU

Running JTZU in DISCOVERONLY mode will search your system for IBM JREs and SDKs. All JREs and SDKs found are listed in the SDKList.txt file, including their current Olson time zone update level. To see which time zone updates are included, see Olson time zone updates for Java JRE and SDK service refreshes for IBM products.

For more information and to download JTZU, see IBM Time Zone Update Utility for Java Download Page .

---

Change history

Date	Description
03 Nov 2011	Removed the outdated TimeTest.jar and related instructions. Added Java 7.
10 Nov 2009	Updated references to IBM i
13 Jul 2009	Updated links to Olson time zone page
15 May 2009	Editorial updates
6 April 2009	Changed links provided to remove links to archived document (SWG21250511)
10 Nov 2008	Added Java 6.0 to choice table
23 Sep 2007	Update to TimeTest.jar for JTZU 1.3.7g
19 Sep 2007	Update to TimeTest.jar
19 Aug 2007	Generalise document to provide information for future DST changes.
02 Mar 2007	Link to more test cases.
21 Feb 2007	Fix to TimeTest. Using Perth for Australia instead of Sydney, as Sydney is in New South Wales.
20 Feb 2007	New version of TimeTest.jar. Works on 1.3.1, reports more information.
16 Feb 2007	Add information on running TimeTest.jar
15 Feb 2007	Added information about when you have a choice between service and JTZU
23 Jan 2007	Added table of Java update methods
13 Dec 2006	Initial publication

[attachment "TimeTest-20070923.jar" deleted by Sue Chaplain/UK/IBM]