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:17] – mmacgregorwhy_did_time_change_in_the_wrong_month [2019/07/25 03:28] – mmacgregor
Line 24: Line 24:
 ==== 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) ====
  
 +<code>
 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 56: Line 57:
    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 March 11th date for 2007.  You are now finished.
 +</code>
  
 ==== VAX/Alpha 6.2 (and variants), VAX 7.3 ==== ==== VAX/Alpha 6.2 (and variants), VAX 7.3 ====
  
 +<code>
 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 90: Line 92:
       $ DTSS$SET_TIMEZONE := $SYS$SYSTEM:DTSS$SET_TIMEZONE.EXE       $ DTSS$SET_TIMEZONE := $SYS$SYSTEM:DTSS$SET_TIMEZONE.EXE
       $ DTSS$SET_TIMEZONE MODIFY       $ DTSS$SET_TIMEZONE MODIFY
 +</code>
  
 ==== ALPHA 7.3 or 7.3-1 ==== ==== ALPHA 7.3 or 7.3-1 ====
  
 +<code>
 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
 system is in another timezone, you will have to modify it to the appropriate  system is in another timezone, you will have to modify it to the appropriate 
Line 146: Line 149:
    listed in TDF$UTC_STARTUP.COM so that your logicals will be correct after     listed in TDF$UTC_STARTUP.COM so that your logicals will be correct after 
    system boots.  No reboot is necessary at this time.    system boots.  No reboot is necessary at this time.
 +</code>
  
 ==== ALPHA 7.3-2, ALPHA/ITANIUM 8.2, ITANIUM 8.2-1 ==== ==== ALPHA 7.3-2, ALPHA/ITANIUM 8.2, ITANIUM 8.2-1 ====
  
 +<code>
 1. Apply the appropriate patch of:  VMS732_TZ-V0300, VMS82A_TZ-V0200, 1. Apply the appropriate patch of:  VMS732_TZ-V0300, VMS82A_TZ-V0200,
    VMS82I_TZ-V0200, VMS821I_TZ-V0200    VMS82I_TZ-V0200, VMS821I_TZ-V0200
Line 163: Line 166:
    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 next appropriate time change date.  You are now finished.
  
 3.  *IF* running AUTO_DLIGHT_SAV = 1: 3.  *IF* running AUTO_DLIGHT_SAV = 1:
Line 176: Line 179:
 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  +   After 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. 
 +</code>
  
  
 +==== ALPHA / I64 8.3 ====
  
-==== ALPHA/I64 8.3 ==== +<code> 
- +For the US customers, the solution is already built into the OpenVMS codestream. 
- +For Canadian customers, it depends on which Provence your machine is located.   
-For the US customers, the solution is already built into the OpenVMS codestream, +If you are in the Mountain or Pacific timezones, your timezones may not be correct.   
-treat 2007 the same as you did in 2006.  For Canadian customers, it depends on  +You can check by looking at your SYS$TIMEZONE_RULE logical.  If it shows:   
-which Provence your machine is located.  If you are in the Mountain or Pacific  +
-timezones, your timezones may not be correct.  You can check by looking at your  +
-SYS$TIMEZONE_RULE logical.  If it shows:   +
  
    "...M3.2.0/02,M11.1.0/02"     "...M3.2.0/02,M11.1.0/02" 
  
 then you are operational.  If it doesn't show that, then install the appropriate then you are operational.  If it doesn't show that, then install the appropriate
-of VMS83A_TZ-V0100 or VMS83I_TZ-V0100 +patch of either VMS83A_TZ-V0100 or VMS83I_TZ-V0100 
- +</code>
- +
-==== ALPHA/I64 8.4 and above ====+
  
 +==== ALPHA / I64 8.4 and above ====
  
 +<code>
 The solution is already build into the OpenVMS codestream. The solution is already build into the OpenVMS codestream.
 +</code>
  
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