Australia - Updated: 28th March 2006
hp.com home products and services support and drivers solutions how to buy
» contact hp
hp.com home HP Services, South Pacific
» Sydney CSC home page

Navigation
» ECOinfo main index
» Search ECOs
» Search FTP site
» Browse FTP site

ECO Indexes
» Chronological Index
» Indexed by Version
» Indexed by Rating
» Alpha Indexed by Name
» VAX Indexed by Name
» On Hold List

Associated Links
» OpenVMS Home Page
» OpenVMS News
» DIA/WIS Web Service

Feedback
» mail to CSC
.
Sydney Customer Support Centre

HP Mission Critical Advisory on Daylight Saving Changes in Australia

28th March 2006

With the Commonwealth Games in Melbourne this year the changeover date for daylight savings has been moved from last week of March to first week of April.

This means instead of daylight saving time ending on Sunday 26th of March 2006, it will end on Sunday 2nd of April 2006. This change is only for the year 2006.

The change applies to these areas:

  • Australian Capital Territory (which tracks New South Wales)
  • Broken Hill (which tracks South Australia)
  • Lord Howe Island
  • New South Wales
  • South Australia
  • Tasmania
  • Victoria
As a result of this change, computer systems will show incorrect time between 26th March and 2nd April, if their time zone definitions predate the change. This will affect applications that depend on the system time for recording or reporting data. This also affects customers who record data from Australian sources, that have to interoperate with Australian offices, or who run hosting servers with an Australian time zone.

If a fix is not implemented, applications will experience the following problems:

  1. the system will be running one hour ahead of the correct time during the affected one-week window,

  2. results for date and time operations for dates in this 2006 window will be one hour ahead of the correct time.

    This will be true regardless of when the application is executing. That is, if it is running in 2007, it will still get the wrong results for dates that fall in this 2006 window. Results for dates that fall in this window for any other year will be correct.

To address these changes for different operating systems please refer to the information elsewhere on this page:

HP-UX Time Zone Updates

21st March 2006

Many customers require an update for HP-UX and HP-UX Java.

For HP-UX, we have released patches to update the tztab file to fix the problem:

  • HP-UX 11.23, PHCO_34375 s700_800 11.23 tztab(4) cumulative patch,
  • HP-UX 11.11, PHCO_34342 s700_800 11.11 tztab(4) cumulative patch,
  • HP-UX 11.00, PHCO_34266 s700_800 11.00 tztab(4) cumulative patch.
These patches can be obtained from ITRC (registration is required) or your support channel.

HP-UX Java also needs to be aware of the new DST rules for 2006. This is addressed by upgrading to a new version of Java with the updated time zone information. If the Java changes are not implemented, regardless of whether or not HP-UX has been patched, Java-based applications will experience the same problems noted above.

Depending on the release line that you are currently using, HP encourages you to upgrade to the latest version of Java as follows:

  • for HP-UX Java JDK 5.0, HP encourages you to upgrade to 5.0.03, available on the HP-UX Java website, www.hp.com/go/java. This version provides the correct results for all dates in 2006 and beyond, regardless of when the application is executed.

  • for HP-UX Java SDK 1.4.2, HP encourages you to upgrade to 1.4.2.10a, available via your normal HP support channel. This version provides the correct results for all dates in 2006 and beyond, regardless of when the application is executed.

  • for HP-UX Java SDK 1.3.1, HP encourages you to upgrade to 1.3.1.18, available (after March 22, 2006) on the HP-UX Java website, www.hp.com/go/java. This version provides the correct results for dates during the affected one-week window, in 2006 only, and when executed during 2006 only. Please refer to 1.3.1.18 Release Notes for a complete description of the problem and solution.

Linux Time Zone Updates

21st March 2006

On SUSE Enterprise Linux from Novell, we are not aware of any updates yet, but the manual process works fine.

On Red Hat Enterprise Linux, updates are available from Red Hat:

Note: remember to run system-config-date as the instructions say, or the zdump test will pass but the time will not rollover. This is because the /etc/localtime file is a copy of the zoneinfo file.

The manual workaround is to adopt the /usr/share/zoneinfo/Australia file from a later version, or use /usr/sbin/zic to compile the revised australasia file from the later source package. Call for assistance.

A method to determine for any RPM-based Linux distribution what package is responsible for providing the time zone files is;

# TZ=:Australia/NSW strace -e open date
...
[take note of file used by the date command]
# rpm -qif /usr/share/zoneinfo/Australia/NSW
For Debian GNU/Linux, see Bug #345479 for status and a workaround of replacing the file.

Tru64 Time Zone Updates

27th February 2006

Here are pointers to patches that correct the time zone files. Choose the version that matches your version of Tru64 UNIX:

If you wish to maintain the zoneinfo sources yourself rather than install the patch, edit /etc/zoneinfo/sources/australasia to add the new rule and run /usr/bin/zic on the edited file. For example, for New South Wales:

...
Rule    AN      1996    2005    -       Mar     lastSun 2:00s   0 -
Rule    AN      2006    only    -       Apr     Sun>=1  2:00s   0 -
Rule    AN      2007    max     -       Mar     lastSun 2:00s   0 -
...
Compile this with the zone info compiler:

# /usr/bin/zic /etc/zoneinfo/sources/australasia
Check that the changes have taken effect, by examining the discontinuities:

# zdump -c 2007 -v Australia/Sydney | grep 2006
This alternative method is supported. Configuration files in /etc are customer editable.

Microsoft Windows Time Zone Updates

17th January 2006

Microsoft have already addressed the issue in the following KB:

An update has been created for the following products:

  • Microsoft Windows 2000
  • Microsoft Windows Millennium Edition (Me)
  • Microsoft Windows Server 2003
  • Microsoft Windows XP
The update will add new time zone rules to the registry. The time zones have been named as follows to make sure that they are clearly identified as only for the year 2006:

  • (GMT+10:00) Canberra, Melbourne, Sydney (Commonwealth Games)
  • (GMT+10:00) Hobart (Commonwealth Games)
  • (GMT+09:30) Adelaide (Commonwealth Games)
The hotfix for this KB is publicly available. The IA64 (64 Bit Itanium) version is still under review, more information on this will be provided as soon as it becomes available.

OpenVMS Time Zone Updates

21st March 2006

A command procedure has been developed by the regional OpenVMS support team to address the Daylight Saving changes caused by the Commonwealth Games. Please log a support call for the procedure.

For OpenVMS Java 1.3.1, 1.4.2 and 1.5.0, contact HP for specific patches.

OpenVMS V7.2-2 and V7.3 Upgrade Warning

1st March 2002

Upgrades to OpenVMS V7.2-2 or V7.3 may fail at the 60% mark with a DUPKEY error reported against STARLET.OLB. The only supported recovery path from the failure is to restore the system disk from backup and restart the upgrade. The condition results from an incompatibility between FORRTL and/or COBRTL modules present in STARLET.OLB and modules provided by the operating system upgrade.

For V7.3 upgrades, the simplest way to avoid the problem is to install the latest versions of FORRTL and COBRTL prior to attempting the upgrade. The installation is quick and simple. There should be no negative consequences of running the latest RTLs. The kits can be found on CD #2 of the OpenVMS/Alpha Software Products Library distribution dated March 2002 or later (CONDIST). The latest versions as of March 2002 can also be downloaded as a self expanding saveset RTLMAR2002.EXE. RUN the downloaded file on an OpenVMS/Alpha system to unpack a saveset containing both RTLs. Use BACKUP to extract the PCSI files and PRODUCT INSTALL to install them.

For V7.2-2 upgrades, if the existing system has had a COBRTL or FORRTL kit installed, the error will occur. It cannot be avoided. For such systems, the Customer Support Centre recommends the latest FORRTL and COBRTL be installed, as described above, prior to the upgrade. When the DUPKEY error occurs, force the installation to proceed. That is, when prompted:

  %PCSI-E-WRITEERR, error writing DISK$SYSDSK:[VMS$COMMON.][SYSLIB]STARLET.OLB
  -LBR-E-DUPKEY, duplicate key in index
  %PCSI-E-OPFAILED, operation failed
  Terminating is strongly recommended. Do you want to terminate? [YES]
you should answer NO. Once the installation has completed, reinstall both the COBRTL and FORRTL kits.

If you have any questions about this warning, please log a case with the Customer Support Centre, mentioning DUPKEY error on upgrade.

OpenVMS Security Update

14th November 2001

A mandatory update to DECwindows on OpenVMS has been released to address a potential security vulnerability in the DECwindows interface. Further information can be found in the FAQ and the ECO is available for download here in Australia.

What are ECOs?
Software Engineering Change Orders (ECOs), or patches, are modifications to software released for customers to use to solve problems experienced.

Attention
In order for Compaq to protect its intellectual property and other legal rights in its software patches, it is necessary to obtain its customers' agreement to Compaq's standard licensing terms in connection with any download. If you access these software patches you are manifesting your legal agreement to the terms of the Digital Software Patch License Agreement.
Public FTP Access
Choose the Browse Patches option to access the selection of patches available to users of Compaq products, whether or not you have a software service contract. Please note that not all software patches are present in this directory as some may be affected by business or export agreements that do not allow their global distribution. 
privacy statement using this site means you accept its terms feedback to the webmaster
VMS rules VMS rocks OpenVMS rules OpenVMS rocks