======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_TZ-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - New Russian TimeZone Rules 2.2 Reboot Requirement: No reboot is necessary after installation of this kit. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0800 - VMS84I_TDF-V0100 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_TZ-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 Russia is undergoing time zones changes from October 26, 2014 at 2:00 local time. 5.2.1.1 Problem Description: According to new law passed by Russia, the below time zones will undergo changes and move permanently to STANDARD TIME (also called WINTER TIME). The new signed law on the calculation of the time from Oct 26th 2014 2:00 (in Russian): http://text.document.kremlin.ru/SESSION/PILOT/loadfavorite.html?page=1&pid=70700518 The users who fall in these below zones should consider installing this patch and resetting their time zones so that the "new rule" becomes active. There are special instructions for setting up the zones before or after 26th Oct 2014-2:00 local time. So please read the instructions below carefully. Below zones will "reduce" their UTC offset by 1. EUROPE/KALININGRAD EUROPE/MOSCOW EUROPE/SIMFEROPOL EUROPE/VOLGOGRAD ASIA/YEKATERINBURG ASIA/OMSK ASIA]NOVOSIBIRSK ASIA/KRASNOYARSK ASIA/IRKUTSK ASIA/YAKUTSK ASIA/VLADIVOSTOK ASIA/SAKHALIN ASIA/SREDNEKOLYMSK[*] Page 3 Below zones will "reduce" their UTC offset by 2. ASIA/CHITA[*] ASIA/MAGADAN Below zones will have no change in their UTC offset, but will switch to Permanent Standard Time. EUROPE/SAMARA ASIA/NOVOKUZNETSK[*] ASIA/KAMCHATKA ASIA/ANADYR [*]Indicates New Time Zones Added to OpenVMS in this Kit. If you reset the time zone before 26th OCT 2014 2:00, then the time will automatically shift(drift) to respective times as mentioned for above zones. Along with time, the DAYLIGHT TIME will shift to STANDARD TIME. If you reset the time zones after 26th OCT 2014 2:00, then the time will be set to STANDARD TIME. The per-requisite for these changes is AUTO_DLIGHT_SAV SYSGEN parameter should be set to "1". Instructions for setting time "before" 26th OCT 2014 2:00: 1. Make sure AUTO_DLIGHT_SAV is set to 1 2. While setting time zone using UTC$TIME_SETUP.COM, make sure to select "This time zone supports daylight saving time" as YES. Rest of the settings you can leave default. Instructions for setting time "after" 26th OCT 2014 2:00: 1. Make sure AUTO_DLIGHT_SAV is set to 1 2. While setting time zone using UTC$TIME_SETUP.COM, make sure to select "This time zone supports daylight saving time" as NO. Rest of the settings you can leave default. On 1st Jan 2015 2:00 local time, the Daylight Saving Time (DST) setting for all the zones will permanently move to STANDARD TIME. Examples: --------------------------------------------------------------------- Before 26th Oct 2014-2:00. $ set time="26-Oct-2014 01:40:59.97" $ @sys$manager:utc$time_setup.com Configuring the Local Time Zone <<<< snip >>>> Press "Return" to redisplay, enter "=" to search or "?" for help, or Page 4 Select the number above that best represents the desired time zone: 20 <<<< snip >>>> Press "Return" to redisplay, enter "=" to search or "?" for help, or Select the number above that best represents the desired time zone: 20 You selected EUROPE / KALININGRAD as your time zone. Is this correct? (Yes/No) [YES]: Configuring the Time Differential Factor (TDF) Default Time Differential Factor for standard time is 2:00. Default Time Differential Factor for daylight saving time is 3:00. <<<< snip >>>> This time zone supports daylight saving time. Is this time zone currently on daylight saving time? (Yes/No): yes Enter the Time Differential Factor [3:00]: <<<< snip >>>> Do you wish to modify the local system time [N]: NEW SYSTEM TIME DIFFERENTIAL FACTOR = 3:00 Is this correct? [Y]: $ @sys$manager:utc$time_setup.com show AUTO_DLIGHT_SAV is set to "1". OpenVMS will automatically change to/from Daylight Saving Time. (in time zones that use Daylight Saving Time) LOCAL TIME ZONE = EUROPE / KALININGRAD -- DAYLIGHT TIME LOCAL SYSTEM TIME = 26-OCT-2014 01:41:40.64 (EEDT) TIME DIFFERENTIAL FACTOR = 3:00 TIME ZONE RULE = EEST^2EEDT^3,M3.5.0/02,M10.4.0/02 Change EEST^ to EEDT^ on the Last Sunday of March (30-Mar-2014) at 02:00 Change EEDT^ to EEST^ on the Fourth Sunday of October (26-Oct-2014) at 02:00 $ set time="26-Oct-2014 01:59:59.97" $ @sys$manager:utc$time_setup.com show AUTO_DLIGHT_SAV is set to "1". OpenVMS will automatically change to/from Daylight Saving Time. (in time zones that use Daylight Saving Time) LOCAL TIME ZONE = EUROPE / KALININGRAD -- STANDARD TIME LOCAL SYSTEM TIME = 26-OCT-2014 01:00:03.92 (EEST) TIME DIFFERENTIAL FACTOR = 2:00 TIME ZONE RULE = EEST^2EEDT^3,M3.5.0/02,M10.4.0/02 Change EEST^ to EEDT^ on the Last Sunday of March (30-Mar-2014) at 02:00 Change EEDT^ to EEST^ on the Fourth Sunday of October (26-Oct-2014) at Page 5 02:00 $ set time="1-jan-2015 01:59:56" $ @SYS$MANAGER:UTC$TIME_SETUP.COM show AUTO_DLIGHT_SAV is set to "1". OpenVMS will automatically change to/from Daylight Saving Time. (in time zones that use Daylight Saving Time) LOCAL TIME ZONE = EUROPE / KALININGRAD -- STANDARD TIME LOCAL SYSTEM TIME = 1-JAN-2015 02:00:02.02 (EEST) TIME DIFFERENTIAL FACTOR = 2:00 TIME ZONE RULE = EET^2 This time zone does not use Daylight Saving Time. --------------------------------------------------------------------- After 26th Oct 2014-2:00. $ sh time 26-OCT-2014 02:00:03 $ @sys$manager:utc$time_setup.com Configuring the Local Time Zone <<<< snip >>>> Press "Return" to redisplay, enter "=" to search or "?" for help, or Select the number above that best represents the desired time zone: 20 <<<< snip >>>> Press "Return" to redisplay, enter "=" to search or "?" for help, or Select the number above that best represents the desired time zone: 20 You selected EUROPE / KALININGRAD as your time zone. Is this correct? (Yes/No) [YES]: Configuring the Time Differential Factor (TDF) Default Time Differential Factor for standard time is 2:00. Default Time Differential Factor for daylight saving time is 3:00. <<<< snip >>>> This time zone supports daylight saving time. Is this time zone currently on daylight saving time? (Yes/No): no Enter the Time Differential Factor [2:00]: <<<< snip >>>> Do you wish to modify the local system time [N]: NEW SYSTEM TIME DIFFERENTIAL FACTOR = 2:00 Page 6 Is this correct? [Y]: $ @sys$manager:utc$time_setup.com show AUTO_DLIGHT_SAV is set to "1". OpenVMS will automatically change to/from Daylight Saving Time. (in time zones that use Daylight Saving Time) LOCAL TIME ZONE = EUROPE / KALININGRAD -- STANDARD TIME LOCAL SYSTEM TIME = 26-OCT-2014 02:00:51.72 (EEST) TIME DIFFERENTIAL FACTOR = 2:00 TIME ZONE RULE = EEST^2EEDT^3,M3.5.0/02,M10.4.0/02 Change EEST^ to EEDT^ on the Last Sunday of March (30-Mar-2014) at 02:00 Change EEDT^ to EEST^ on the Fourth Sunday of October (26-Oct-2014) at 02:00 --------------------------------------------------------------------- Images Affected: - [sys$ZONEINFO.SYSTEM.ASIA]ANADYR. - [sys$ZONEINFO.SYSTEM.ASIA]CHITA. - [sys$ZONEINFO.SYSTEM.SOURCES]EUROPE. - [sys$ZONEINFO.SYSTEM.ASIA]IRKUTSK. - [sys$ZONEINFO.SYSTEM.EUROPE]KALININGRAD. - [sys$ZONEINFO.SYSTEM.ASIA]KAMCHATKA. - [sys$ZONEINFO.SYSTEM.ASIA]KRASNOYARSK. - [sys$ZONEINFO.SYSTEM.ASIA]MAGADAN. - [sys$ZONEINFO.SYSTEM.EUROPE]MOSCOW. - [sys$ZONEINFO.SYSTEM.ASIA]NOVOKUZNETSK. - [sys$ZONEINFO.SYSTEM.ASIA]NOVOSIBIRSK. - [sys$ZONEINFO.SYSTEM.ASIA]OMSK. - [sys$ZONEINFO.SYSTEM.ASIA]SAKHALIN. - [sys$ZONEINFO.SYSTEM.EUROPE]SAMARA. - [sys$ZONEINFO.SYSTEM.EUROPE]SIMFEROPOL. - [sys$ZONEINFO.SYSTEM.ASIA]SREDNEKOLYMSK. - [sys$ZONEINFO.SYSTEM.ASIA]VLADIVOSTOK. Page 7 - [sys$ZONEINFO.SYSTEM.EUROPE]VOLGOGRAD. - [sys$ZONEINFO.SYSTEM.ASIA]YAKUTSK. - [sys$ZONEINFO.SYSTEM.ASIA]YEKATERINBURG. 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases None 5.2.1.2.2 PTR(S) None 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity After V8.4 5.2.1.4 Work-arounds: None 6 FILES PATCHED OR REPLACED: o [SYS$ZONEINFO.SYSTEM.ASIA]ANADYR. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]CHITA. (new file) o [SYS$ZONEINFO.SYSTEM.SOURCES]EUROPE. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]IRKUTSK. (new file) o [SYS$ZONEINFO.SYSTEM.EUROPE]KALININGRAD. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]KAMCHATKA. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]KRASNOYARSK. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]MAGADAN. (new file) o [SYS$ZONEINFO.SYSTEM.EUROPE]MOSCOW. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]NOVOKUZNETSK. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]NOVOSIBIRSK. (new file) Page 8 o [SYS$ZONEINFO.SYSTEM.ASIA]OMSK. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]SAKHALIN. (new file) o [SYS$ZONEINFO.SYSTEM.EUROPE]SAMARA. (new file) o [SYS$ZONEINFO.SYSTEM.EUROPE]SIMFEROPOL. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]SREDNEKOLYMSK. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]VLADIVOSTOK. (new file) o [SYS$ZONEINFO.SYSTEM.EUROPE]VOLGOGRAD. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]YAKUTSK. (new file) o [SYS$ZONEINFO.SYSTEM.ASIA]YEKATERINBURG. (new file) 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_TZ-V0100.ZIPEXE Page 9 7.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS84I_TZ[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO Page 10 o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=HP/BASE=I64VMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_TZ-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_TZ/PRODUCER=HP/BASE=I64VMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, Page 11 HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.