PK41057: EDT TIME ZONE INCORRECTLY MAPS TO EST INSTEAD OF AMERICA/NEW_YORK

APAR status

• Closed as duplicate of another APAR.

Error description

• JVMs containing Olsen time zone data of version 2005r or later
  incorrectly map the Eastern Daylight Time time zone to EST. This
  time zone data is included in Service Refreshes of SR5 or
  greater.
  
  As of SR5, EST's definition has changed (per APAR PK40832).
  
  This causes times parsed by the SimpleDateFormat class to
  incorrectly calculate Daylight Saving Time in certain
  circumstances.
  
  Sun Bug 6530336 documents the technical details of the issue.
  
  USERS AFFECTED:
  Only users at or above SR5, or users which have updated their
  builds using the JTZU utility before version 1.4.7c are
  affected AND either (or both) of the following apply:
  
     1. You use the three letter time zone IDs "EST", "HST", "MST"
  instead of the long format, such as, "America/New_York".
     2. You parse time strings that contain "EDT", "HDT", "MDT".
  
  You are not affected if you are running Java SDK/JRE 1.3.x and
  below.
  

Local fix

• The use of 3-character time zone identifiers has been deprecated
  by Sun since 1998, and IBM customers have been advised to
  eliminate their usage completely in the Java DST Flash issued in
  November 2006:
  http://www.ibm.com/support/docview.wss?rs=3068&uid=swg21250247
  
  The recommended action for a customer to avoid the
  incompatibility problem is to completely eliminate the use of
  3-character values used as a time zone identifier (Time zone
  ID). This means:
  
      * (CASE 1)
        Not using a 3-character value either as the user.timezone
  local setting of the host machine (as an override parameter) or
  by explicitly assigning this setting in a Java application
      * (CASE 2)
        Not coding a 3-character value as the Operating System TZ=
  parameter (which gets passed by the Operating System to Java as
  the default local user.timezone setting of the host machine)
      * (CASE 3 )
        Not coding a 3-character value inside Java API calls as a
  parameter given to the TimeZone.getTimeZone() method in the
  TimeZone class.
  
  Users may also utilize the Java system property:
  ibm.dst.compatibility=true
  in Service Refresh 7 or later to cause EST and MST to retain
  their original pre-SR5 definitions.
  
  See Flash/Alert
  http://www-1.ibm.com/support/docview.wss?rs=3068&uid=swg21256531
  for more information and advice to resolve this issue.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• duplicate of APAR PK42526
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels