PARSEC Technical Information

User Tools

Site Tools

Trace:
why_did_time_change_in_the_wrong_month

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
why_did_time_change_in_the_wrong_month [2019/07/25 03:07] – mmacgregorwhy_did_time_change_in_the_wrong_month [2019/07/25 03:17] – mmacgregor
Line 16: Line 16:
 NOTES: NOTES:
  
-If the VMS version is not listed below and you have questions, then log a call with PARSEC and we'll try and find a solution for you.+If the VMS version is not listed below and you have questions, then log a call with PARSEC at 866-3-PARSEC and we'll find a solution for you.
  
 All of the TZ patches imply that a reboot is not necessary.  This is officially correct, but perhaps misleading.  If you are alpha 7.3 or higher, and you are using the AUTO_DLIGHT_SAV option, then there is a TQE in existance under the JOB_CONTROL process that is currently set to go off in April instead of in March.  Thus, you will either need to stop/restart the JOB_CONTROL process (something we don't really recommend on busy machines, but power users can decide if they can go that route), or reboot the machine.  Either of these steps will correct the TQEs that kick off. All of the TZ patches imply that a reboot is not necessary.  This is officially correct, but perhaps misleading.  If you are alpha 7.3 or higher, and you are using the AUTO_DLIGHT_SAV option, then there is a TQE in existance under the JOB_CONTROL process that is currently set to go off in April instead of in March.  Thus, you will either need to stop/restart the JOB_CONTROL process (something we don't really recommend on busy machines, but power users can decide if they can go that route), or reboot the machine.  Either of these steps will correct the TQEs that kick off.
  
 +All examples below are based on Eastern time.  You will need to modify rules according to your own timezone.  If you aren't sure what the rule should read, contact PARSEC at 866-3-PARSEC
  
-===== VAX/Alpha 6.1, VAX/Alpha 7.1 (and variants), VAX/Alpha 7.2 (and variants) =====+==== VAX/Alpha 6.1, VAX/Alpha 7.1 (and variants), VAX/Alpha 7.2 (and variants) ====
  
 1. *IF* DECnet Phase IV, no change in behavior, use UTC$CONFIGURE_TDF.COM 1. *IF* DECnet Phase IV, no change in behavior, use UTC$CONFIGURE_TDF.COM
  
-2. *IF* DECnet/OSI *AND* no DTSS, then wait until after the 2 a.m. time has +2. *IF* DECnet/OSI *AND* no DTSS, then wait until after the 2 a.m. time on the  
-   been reached and then:+   appropriate date has been reached and then:
  
    a. Execute immediately, and place this command towards the end of your    a. Execute immediately, and place this command towards the end of your
       system startup file:       system startup file:
  
-      $ DEFINE/SYSTEM/EXEC SYS$TIMEZONE_RULE - +      $ DEFINE/SYSTEM/EXEC SYS$TIMEZONE_RULE "EST5EDT4,M3.2.0/02,M11.1.0/02"
-      _$ "EST5EDT4,M3.2.0/02,M11.1.0/02"+
  
-   b. Then, each this time and all future time change dates, issue the  +   b. Then, each this time and all future time change dates, issue the following  
-      following commands:+      commands:
  
       $ INSTALL := $INSTALL       $ INSTALL := $INSTALL
Line 44: Line 44:
 3. *IF* DECnet/OSI *AND* DTSS,  3. *IF* DECnet/OSI *AND* DTSS, 
  
-   Get a copy of the DTSS$TIMEZONE_RULES.DAT included in the VAXTZ01_062 +   Get a copy of the DTSS$TIMEZONE_RULES.DAT included in the VAXTZ01_062 or  
-   or ALPTZ01_062 patch on the web.  Copy this file to your node, then +   ALPTZ01_062 patch on the HPESC website.  Copy this file to your node, then 
    reconfigure the timezones via:    reconfigure the timezones via:
      
Line 58: Line 58:
  
  
-*** VAX/Alpha 6.2 (and variants), VAX 7.3:+==== VAX/Alpha 6.2 (and variants), VAX 7.3 ====
  
 1. *IF* DECnet Phase IV, no change in behavior, use UTC$CONFIGURE_TDF.COM 1. *IF* DECnet Phase IV, no change in behavior, use UTC$CONFIGURE_TDF.COM
Line 82: Line 82:
       system startup file:       system startup file:
  
-      $ DEFINE/SYSTEM/EXEC SYS$TIMEZONE_RULE - +      $ DEFINE/SYSTEM/EXEC SYS$TIMEZONE_RULE "EST5EDT4,M3.2.0/02,M11.1.0/02"
-      _$ "EST5EDT4,M3.2.0/02,M11.1.0/02"+
  
    b. Then, each future time change, issue the following commands:    b. Then, each future time change, issue the following commands:
Line 93: Line 92:
  
  
- +==== ALPHA 7.3 or 7.3-1 ====
- +
-*** ALPHA 7.3 or 7.3-1:+
  
 This procedure is written for the customers in the Eastern timezone.  If your This procedure is written for the customers in the Eastern timezone.  If your
Line 106: Line 103:
 You will need to find a machine that has already installed the TZ patch.  For You will need to find a machine that has already installed the TZ patch.  For
 example, the VMS732_TZ-V0300 or VMS82_TZ-V0200.  If you do not have such a file, example, the VMS732_TZ-V0300 or VMS82_TZ-V0200.  If you do not have such a file,
-you can either log a call with HP to have us FTP the appropriate file to you, +you can pull down one of those patches and issue these commands:
-or you can pull down one of those patches and issue these commands:+
  
   $ CREATE/DIRECTORY [.TIME]   ! good idea to have separate directory   $ CREATE/DIRECTORY [.TIME]   ! good idea to have separate directory
Line 128: Line 124:
  
    $ @SYS$MANAGER:NET$CONFIGURE   and select option 5    $ @SYS$MANAGER:NET$CONFIGURE   and select option 5
- 
  
       [5] Configure Timezone Differential Factor       [5] Configure Timezone Differential Factor
Line 134: Line 129:
    And follow the instructions. This will correct the four SYS$TIMEZONE*     And follow the instructions. This will correct the four SYS$TIMEZONE* 
    logicals immediately and change the "next TDF" time within DTSS to reflect     logicals immediately and change the "next TDF" time within DTSS to reflect 
-   the March 11th date for 2007.  You are now finished.+   the proper Sunday in the future.  You are now finished.
  
 3.  *IF* running AUTO_DLIGHT_SAV = 1: 3.  *IF* running AUTO_DLIGHT_SAV = 1:
Line 147: Line 142:
 4. *IF* Neither DTSS nor AUTO_DLIGHT_SAV, thus "by hand" 4. *IF* Neither DTSS nor AUTO_DLIGHT_SAV, thus "by hand"
  
-   At 2 a.m on March 11th, you will run the UTC$TIME_SETUP.COM, which will  +   At 2 a.m on the appropriate Sunday, you will run the UTC$TIME_SETUP.COM,  
-   correct the four SYS$TIMEZONE* logicals, and change the rule listed in  +   which will correct the four SYS$TIMEZONE* logicals, and change the rule  
-   TDF$UTC_STARTUP.COM so that your logicals will be correct after system +   listed in TDF$UTC_STARTUP.COM so that your logicals will be correct after  
-   boots.  No reboot is necessary at this time.+   system boots.  No reboot is necessary at this time. 
  
 +==== ALPHA 7.3-2, ALPHA/ITANIUM 8.2, ITANIUM 8.2-1 ====
  
-*** ALPHA 7.3-2, ALPHA/ITANIUM 8.2, ITANIUM 8.2-1: 
  
 1. Apply the appropriate patch of:  VMS732_TZ-V0300, VMS82A_TZ-V0200, 1. Apply the appropriate patch of:  VMS732_TZ-V0300, VMS82A_TZ-V0200,
Line 187: Line 183:
  
  
-*** ALPHA/I64 8.3:+==== ALPHA/I64 8.3 ==== 
  
 For the US customers, the solution is already built into the OpenVMS codestream, For the US customers, the solution is already built into the OpenVMS codestream,
Line 201: Line 198:
  
  
-*** ALPHA/I64 8.4 and above:+==== ALPHA/I64 8.4 and above ==== 
  
 The solution is already build into the OpenVMS codestream. The solution is already build into the OpenVMS codestream.
  
why_did_time_change_in_the_wrong_month.txt · Last modified: 2019/07/25 03:39 by mmacgregor
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki