The relevant links are in the "backward" file in the time zone package. --ado From: Fulvio.Bozzo@Sun.COM [mailto:Fulvio.Bozzo@Sun.COM] Sent: Tuesday, March 09, 2010 2:13 To: tz@lecserver.nci.nih.gov; Olson, Arthur David (NIH/NCI) [E] Cc: Yonson.Serrano@Oracle.Com; Armando Paladino; Juan Enrique Coriat Nugent; Rafael Rivero; Julio Carrasco Subject: Fwd: Chile Time Change Arthur, May you consider the former Chilean TZ aliases named Chile/Continental & Chile/EasterIsland into your definition for compatibility issues ? regards, Fulvio. Begin forwarded message: From: Yonson Serrano <yonson.serrano@oracle.com<mailto:yonson.serrano@oracle.com>> Date: March 9, 2010 3:50:58 PM GMT-03:00 To: Fulvio Bozzo <Fulvio.Bozzo@Sun.COM<mailto:Fulvio.Bozzo@Sun.COM>> Cc: Armando Paladino <Armando.Paladino@Sun.COM<mailto:Armando.Paladino@Sun.COM>>, Rafael Rivero <Rafael.Rivero@Sun.COM<mailto:Rafael.Rivero@Sun.COM>>, "Juan E. Coriat - Sun Microsystems" <Juan.Coriat@Sun.COM<mailto:Juan.Coriat@Sun.COM>>, Julio Carrasco <Julio.Carrasco@Sun.COM<mailto:Julio.Carrasco@Sun.COM>> Subject: Re: Chile Time Change Reply-To: yonson.serrano@oracle.com<mailto:yonson.serrano@oracle.com> Hi, (JAVA) tzupdater and the OS patch are separate things. Each one of them requires it's own steps. The IDR OS patch from Nakano (my previous email) will NOT address the tzupdater side of things. The IDR OS patch is build against this data ftp://elsie.nci.nih.gov/pub/tzdata2010e.tar.gz If that data does not have entries for: Link America/Santiago Chile/Continental Link Pacific/Easter Chile/EasterIsland Then the IDR OS patch also will not have those entries. The Olson data reflect the official timezone settings for worldwide use. If more(extra) entries need to be in that data file for Chile, then that request needs to be submitted to: Olson, Arthur David (NIH/NCI) [E] olsona@dc37a.nci.nih.gov<mailto:olsona@dc37a.nci.nih.gov> and tz@elsie.nci.nih.gov<mailto:tz@elsie.nci.nih.gov> Hope this helps, Yonson On 03/09/10 10:31, Fulvio Bozzo wrote: Yonson, Thanks for your email, we also saw the Olson files today for the OS, the changes even if they aren´t identical gives the same result, so it´s ok, but the only thing I miss on that file are the links for some timezone aliases like Chile/Continental and Chile/EasterIsland, many systems are set to Chile/Continental as formerly was the only TZ for us Solaris 8 and earlier releases, so I am missing the links sections into the Olson file: Link America/Santiago Chile/Continental Link Pacific/Easter Chile/EasterIsland They need to be included right? We will be waiting for the today´s patch, as many customers are calling us, thanks. One more question, that patch will include the tzupdater changes, we don't see them updated already. Regards, Fulvio. On Mar 9, 2010, at 2:48 PM, Yonson Serrano wrote: Armando, When a DST change is made, there are three things that need to be updated in regards to DST: the OS, Java, and Calendar Server. 1) OS: I took a look at the info you sent me and it looks ok, however I CANNOT bless it or validate it. The new Olson data with the DST Chile changes came out yesterday and is located at: ftp://elsie.nci.nih.gov/pub/tzdata2010e.tar.gz I have our asked our engineer (nobutomo.nakano@sun.com<mailto:nobutomo.nakano@sun.com>) who generates the official OS patches, how soon he can have an interim patch out with the Chile changes in place. I expect to hear from him today. I will let you know ASAP. 2) JAVA: The info you provided on the Java end looks correct. You will need to use the data file in the link above to get the Chile changes in. I am also confirming this with the Java DST team. I do not expect any issues. 3) Calendar: I have provide an example below (Argentina) on how to implement these changes. The write up below is old....so the stuff about the hot fix might be dated and can be ignored. The example write is between the ******* lines. I expect to be in contact with you later today with the follow up info per above. Thanks, Yonson ********************************************************************** Follow-ups to: Christomer Simons or Chuck Neild for questions. Please add this to your calendar server timezone.ics file. You will notice that each entry has a BEGIN:VTIMEZONE and a END:VTIMEZONE seperated by a space. Add this to the timezone.ics file before the end tags. Stop and then start the calendar server for the changes to take effect. There are a few things to keep in mind. One is that you need to make sure that the OS, along with the Jre is also patched with the proper updates. I also recommend that you have the latest calendar server patch on the system. I have provided you the latest hotfix for the calendar server (5.1.1) located (below). If the customer is not using the 5.1.1, it is still the same fix. It is just recommended that what ever version (assuming 6.x) of the calendar server, that you are on the latest patch. ftp://supportfiles.sun.com/cores/iplanetdownloads/ics-5.1.1hf1.28-export-en-de-es-fr-c-ja.sparc-sun-solaris2.6.tar.gz Steps to apply timezone fix 1)Stop the calendar server, and back up 2)Apply hotfix 3)Apply changes to the timezone.ics file 4)Start calendar system Remember you must also have the OS and Jre patches applied also. BEGIN:VTIMEZONE TZID:America/Buenos_Aires X-S1CS-TZID-ALIAS:SA Eastern Standard Time BEGIN:STANDARD DTSTART:20071230T000000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=12 TZOFFSETFROM:-0200 TZOFFSETTO:-0300 TZNAME:ART TZNAME:GFT TZNAME:EST TZNAME:UYST TZNAME:SRT END:STANDARD BEGIN:DAYLIGHT DTSTART:20080316T000000 RRULE:FREQ=YEARLY;BYDAY=3SU;BYMONTH=3 TZOFFSETFROM:-0300 TZOFFSETTO:-0200 TZNAME:ART TZNAME:GFT TZNAME:EST TZNAME:UYST TZNAME:SRT END:DAYLIGHT X-NSCP-TZCROSS:20071230T030000Z;20080316T020000Z; END:VTIMEZONE ********************************************************************** On 03/09/10 09:06, Armando Paladino wrote: Yonson, As per our conversation I am sending the document we discusses. As you explained to me, you would be able to generate the needed patches for Chile that would cover Solaris and Java and that would be the best option to pursue. Waiting for your communication. (You can reply to this mail with questions and/or concerns) Best Regards, Armando On 3/9/2010 9:37 AM, Rafael Rivero wrote: Armando, Como sabes, debido a la tragedia en Chile el gobierno decidió posponer por este año solamente el cambio de hora que estaba fijado para el segundo domingo de Marzo (Exactamente el 13 de Marzo a las 23:59:59) y decidió aplazarlo hasta el primer domingo de Abril (03 de Abril a las 23:59:59). Aquí te estoy pasando los cambios que hemos estado probando en nuestro Lab. con buenos resultados en Solaris 9 y 10 Todavía nos falta probar en Solaris 8, ya que en esta versión tenemos el problema que sólo existía el Timezone Chile/Continental por lo que el archivo de la versión de Solaris 10, tuvo problemas la ultima vez que se aplicó en los clientes que tenían Solaris 8 desde una versión de Kernel hacia atrás. El efecto que sucedió en esa oportunidad, fue que la Zona Chile/Continental quedara con un archivo de size 0, dado que el link se hacia de un archivo inexistente hacia este. Frente a esto, tenemos dos opciones a nuestro parecer: 1.- Elaborar una archivo específico para Solaris 8 (Antiguos) 2.- Conocer cual es el parche que hace que las versiones de Solarios 8 antiguas tengan el timezone America/Santiago. Ademas de esto, también falta armar la solución para Java, en el siguiente link: http://java.sun.com/javase/tzupdater_README.html encontramos la siguiente sección: Pero por lo que veo esto solo remueve los cambios aplicados del ultimo tzupdater, y el próximo 3 de abril Java no cambiaría la hora. Removing TZUpdater Tool Changes <Mail Attachment.gif> You must stop any running instances of the JDK/JRE software to be operated upon before you run the TZupdater tool on that installed JDK/JRE software image. There is currently no option to remove TZUpdater modifications. By following these steps, you can manually remove the modifications made by the current TZUpdater tool: 1. Locate the zi directory under the modified JAVAHOME/jre/lib directory. This is the newer data. 2. Locate a zi.tzdata* directory in the same JAVAHOME/jre/lib directory. This is the replaced, older data. 3. Obtain the currently installed timezone data version from the command java -jar tzupdater.jar -V. 4. Rename the current zi directory to something like zi.tzdata2007g, or whatever version was given by the command in step 3. Ensure this does not conflict with the older data directory. 5. Rename the older data directory to zi. 6. Validate the change in currently active timezone data by executing java -jar tzupdater.jar -V. 7. Restart applications on this JDK/JRE instance as desired. Cual seria el procedimiento a seguir en este caso??? ***************************************************** Procedimiento realizado en Lab ***************************************************+ 1.- Backup de archivos - Backup de archivos zoneinfo /usr/share/lib/zoneinfo/America/Santiago /usr/share/lib/zoneinfo/Pacific/Easter /usr/share/lib/zoneinfo/Chile/Continental /usr/share/lib/zoneinfo/Chile/EasterIsland {Example using tar} # tar cvf /var/tmp/backup.tar \ /usr/share/lib/zoneinfo/America/Santiago \ /usr/share/lib/zoneinfo/Pacific/Easter \ /usr/share/lib/zoneinfo/Chile/Continental \ /usr/share/lib/zoneinfo/Chile/EasterIsland - Back de archivo fuente #cp /usr/share/lib/zoneinfo/src/southamerica /usr/share/lib/zoneinfo/src/southamerica.old 2.- Verificar las reglas actuales # zdump -v Chile/Continental | grep "2010" Chile/Continental Mon Mar 8 15:16:03 2010 UTC = Mon Mar 8 12:16:03 2010 CLST isdst=1 Chile/Continental Sun Mar 14 02:59:59 2010 UTC = Sat Mar 13 23:59:59 2010 CLST isdst=1 Chile/Continental Sun Mar 14 03:00:00 2010 UTC = Sat Mar 13 23:00:00 2010 CLT isdst=0 Chile/Continental Sun Oct 10 03:59:59 2010 UTC = Sat Oct 9 23:59:59 2010 CLT isdst=0 Chile/Continental Sun Oct 10 04:00:00 2010 UTC = Sun Oct 10 01:00:00 2010 CLST isdst=1 # ***** Realizar las siguientes modificaciones en el archivo /usr/share/lib/zoneinfo/src/southamerica Rule Chile 2009 only - Mar Sun>=9 3:00u 0 - Rule Chile 2010 only - Apr Sun>=1 3:00u 0 - Rule Chile 2011 max - Mar Sun>=9 3:00u 0 - Zone America/Santiago -4:42:46 - LMT 1890 -4:42:46 - SMT 1910 -5:00 - CLT 1916 Jul 1 -4:42:46 - SMT 1918 Sep 1 -4:00 - CLT 1919 Jul 1 -4:42:46 - SMT 1927 Sep 1 -5:00 Chile CL%sT 1947 May 22 -4:00 Chile CL%sT Zone Pacific/Easter -7:17:44 - LMT 1890 -7:17:28 - EMT 1932 Sep -7:00 Chile EAS%sT 1982 Mar 13 21:00 -6:00 Chile EAS%sT Link America/Santiago Chile/Continental Link Pacific/Easter Chile/EasterIsland 3.- Update zoneinfo database using zic(1M) This command will create and install the new files listed in 2). # /usr/sbin/zic /usr/share/lib/zoneinfo/src/southamerica 4.- Revision de archivos # zdump -v America/Santiago | grep "2010" America/Santiago Mon Mar 8 15:27:18 2010 UTC = Mon Mar 8 12:27:18 2010 CLST isdst=1 America/Santiago Sun Apr 4 02:59:59 2010 UTC = Sat Apr 3 23:59:59 2010 CLST isdst=1 <<<<<<<<<<<<< Cambio de Hora America/Santiago Sun Apr 4 03:00:00 2010 UTC = Sat Apr 3 23:00:00 2010 CLT isdst=0 <<<<<<<<<<<<< Cambio de Hora America/Santiago Sun Oct 10 03:59:59 2010 UTC = Sat Oct 9 23:59:59 2010 CLT isdst=0 America/Santiago Sun Oct 10 04:00:00 2010 UTC = Sun Oct 10 01:00:00 2010 CLST isdst=1 # # zdump -v Chile/Continental | grep "2010" Chile/Continental Mon Mar 8 15:41:29 2010 UTC = Mon Mar 8 12:41:29 2010 CLST isdst=1 Chile/Continental Sun Apr 4 02:59:59 2010 UTC = Sat Apr 3 23:59:59 2010 CLST isdst=1 <<<<<<<<<<<<< Cambio de Hora Chile/Continental Sun Apr 4 03:00:00 2010 UTC = Sat Apr 3 23:00:00 2010 CLT isdst=0 <<<<<<<<<<<<< Cambio de Hora Chile/Continental Sun Oct 10 03:59:59 2010 UTC = Sat Oct 9 23:59:59 2010 CLT isdst=0 Chile/Continental Sun Oct 10 04:00:00 2010 UTC = Sun Oct 10 01:00:00 2010 CLST isdst=1 # 5.- Reboot system ************************ Fin procedimiento *********************** En el site de Olso (ftp://elsie.nci.nih.gov/pub/) ya esta la actualización de el archivo southamerica (tzdata2010e.tar.gz), pero aun no contempla la problemática de Chile/Continental De antemano muchas gracias por tu ayuda, Atentamente, -- <Mail Attachment.gif><http://www.sun.com/> Lcdo. Rafael Rivero B. Customer Facing Engineer Sun Microsystems, Inc. Sánchez Fontecilla 310, 5th floor. Las Conde, Santiago de Chile. CP. 7550000 Phone +56-2-3724500 Fax +56-2-3724560 Email Rafael.Rivero@Sun.COM<mailto:Rafael.Rivero@Sun.COM> <Mail Attachment.gif><http://www.sun.com/> -- <Mail Attachment.gif><http://www.sun.com/> Lcdo. Rafael Rivero B. Customer Facing Engineer Sun Microsystems, Inc. Sánchez Fontecilla 310, 5th floor. Las Conde, Santiago de Chile. CP. 7550000 Phone +56-2-3724500 Fax +56-2-3724560 Email Rafael.Rivero@Sun.COM<mailto:Rafael.Rivero@Sun.COM> <Mail Attachment.gif><http://www.sun.com/> -- <Mail Attachment.gif><http://www.oracle.com/> Yonson Serrano | GCS North America yonson.serrano@oracle.com<mailto:yonson.serrano@oracle.com> Strategic Customer Manager, SCM Phone: +1 925 737-5312 | x45312 Oracle Global Customer Services <Mail Attachment.gif><http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment Regards, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Fulvio Bozzo Client Delivery Manager - ACC Region Sun Microsystems E-mail: Fulvio.Bozzo@Sun.com<mailto:Fulvio.Bozzo@Sun.com> Phone: +56 (2) 3724551 Internal: x58351 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Regards, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Fulvio Bozzo Client Delivery Manager - ACC Region Sun Microsystems E-mail: Fulvio.Bozzo@Sun.com<mailto:Fulvio.Bozzo@Sun.com> Phone: +56 (2) 3724551 Internal: x58351 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.