iManager Timezone change in United States and Canada 2007, Australia 2006

  • 3867097
  • 27-Jun-2007
  • 26-Apr-2012


Novell iManager 2.5
Novell iManager 2.6
Novell Tomcat on NetWare


Daylight Saving Time in the United States and Canada is changing.
Western Australia Daylight Saving Time Change

iManager on each of the supported platforms uses some form of Tomcat which is dependent on JAVA. On NetWare, we use the existing JVM that is already installed. On the non-NetWare platforms, we lay down a standalone Java package that needs to be updated with the new Daylight Savings changes.

The Java Runtime Environment (JRE) stores rules about DST observance all around the globe. Older JREs will have outdated rules that will be superseded by the Energy Policy Act of 2005. As a result, applications running on an older JRE may report incorrect time from March 11, 2007 through April 2, 2007 and from October 29, 2007 through November 4, 2007.

New Zealand has decided to change their daylight savings start and end times.


Sun has released information on what needs to be updated to avoid this problem. The link to the article on Sun's website can be found by going to:

The article states that if running the following Java versions, you do not have to run the update:

Java SE 6 or later
J2SE 5.0 Update 6 or later
J2SE 1.4.2_11 or later
J2SE 1.3.1_18 or later

There has also been some additional countries that have decided to change their daylight savings start and end times (Haiti, Turks and Caicos, and New Zealand)

For version 1.4 or later, Sun has made available a tool that will modify the time zone data within the existing JRE. The name of the tool is "tzupdater" and can be found by going to

In order to receive the latest fixes for New Zealand, verify that the version of the tzupdater tool you are using is at least version tzupdater-1_2_1-2007f or greater.

NOTE: You will be required to setup a free user account with Sun in order to download the tool.

Once downloaded, extract the tzupdater.jar file and copy the file to the following locations depending on your platform.

NetWare: run from server command prompt
Windows: C:\Program Files\Novell\jre\bin
Solaris: /opt/novell/jre/bin
OES Linux: /usr/lib/java/jre/bin ($JAVA_HOME should be /usr/lib/java)
Non-OES Linux: /opt/novell/j2sdk/java_version_dir/bin
iManager Workstation on Windows:dir_path\imanager\bin\windows\java\bin
iManager Workstation on Linux:dir_path\imanager\bin\linux\java\bin

IMPORTANT: It is critical that when running the tzupdater tool that you run the java executable from the specified directory above or else the java that will be updated may not be the specific one that iManager uses.

Run the command using the following syntax to first see if your JAVA needs the update:

java -jartzupdater.jar -t (-t is for test only. No changes are made)

This will run through a series of tests and will report whether the test succeeded or failed for a large number of different time zones. It may also report time zones that were not found. This is normal. If at the end of the test it states that "Validation tests failed", then you need to run the utility. If none of this is displayed and the java utility simply exits with no errors, then your JAVA is up to date already.

To update the timezones, run the following command.

java -jar tzupdater.jar -u -v -bc -f (-u runs the update, -v is for verbose, -f is for force, -bc resolves Sun Alert 102836)

If successful, you should see something similar to:

Validating the new time zone data . . . done.
Time zone data update is complete.

NOTE: On NetWare you must also delete the following 3 files located in the SYS:\java\lib\zi directory:


If you run the utility once again with the -t switch, it should just exit without reporting any problems or errors. If so then you are done.


Top Issue

Additional Information