why_did_time_change_in_the_wrong_month
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
why_did_time_change_in_the_wrong_month [2019/07/25 03:17] – mmacgregor | why_did_time_change_in_the_wrong_month [2019/07/25 03:39] (current) – mmacgregor | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | This is a work in progress | ||
====== Why did the system time change in the wrong month? ====== | ====== Why did the system time change in the wrong month? ====== | ||
- | There are a variety of reasons that may explain this situation and before we discuss the other possibilities, | + | There are a variety of reasons that may explain this situation and before we discuss the other possibilities, |
- | Prior to that change, the Public Utility Holding Company Act of 1935 dictated that time would change within the US as follows. The first Sunday of April at 2 a.m and the final Sunday of October at 2 a.m. | + | Prior to that change, the Public Utility Holding Company Act of 1935((2 Public Utility Holding Company Act of 1935: https:// |
After the change, the rules changed to to the second Sunday of March at 2 a.m. and the first Sunday of November at 2 a.m. | After the change, the rules changed to to the second Sunday of March at 2 a.m. and the first Sunday of November at 2 a.m. | ||
- | The HP OpenVMS engineering group made the decision to provide patches for some versions of OpenVMS, but not all of them. Thus, several | + | The HP OpenVMS engineering group made the decision to provide patches for some versions of OpenVMS, but not all of them. Thus, several |
- | + | ||
- | Any VMS version listed below before OpenVMS 8.4 are officially *UNSUPPORTED*. | + | |
+ | The solutions listed below are for your benefit, PARSEC cannot guarantee its effectiveness because of the possibility of error in transmitting or implementing it. It is meant to be used as a template for writing your own solution, and it may require modification for use on your system. | ||
NOTES: | NOTES: | ||
Line 18: | Line 16: | ||
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. | 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. | + | All of the TZ patches imply that a reboot is not necessary. |
All examples below are based on Eastern time. You will need to modify rules according to your own timezone. | All examples below are based on Eastern time. You will need to modify rules according to your own timezone. | ||
Line 24: | Line 22: | ||
==== 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 | ||
Line 56: | Line 55: | ||
| | ||
the March 11th date for 2007. You are now finished. | the March 11th date for 2007. You are now finished. | ||
+ | </ | ||
==== 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 90: | Line 90: | ||
$ DTSS$SET_TIMEZONE := $SYS$SYSTEM: | $ DTSS$SET_TIMEZONE := $SYS$SYSTEM: | ||
$ DTSS$SET_TIMEZONE MODIFY | $ DTSS$SET_TIMEZONE MODIFY | ||
+ | </ | ||
==== 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. | This procedure is written for the customers in the Eastern timezone. | ||
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 147: | ||
| | ||
| | ||
+ | </ | ||
==== ALPHA 7.3-2, ALPHA/ | ==== ALPHA 7.3-2, ALPHA/ | ||
+ | < | ||
1. Apply the appropriate patch of: VMS732_TZ-V0300, | 1. Apply the appropriate patch of: VMS732_TZ-V0300, | ||
| | ||
Line 163: | Line 164: | ||
And follow the instructions. This will correct the four SYS$TIMEZONE* | And follow the instructions. This will correct the four SYS$TIMEZONE* | ||
| | ||
- | | + | |
3. *IF* running AUTO_DLIGHT_SAV = 1: | 3. *IF* running AUTO_DLIGHT_SAV = 1: | ||
Line 176: | Line 177: | ||
4. *IF* Neither DTSS nor AUTO_DLIGHT_SAV, | 4. *IF* Neither DTSS nor AUTO_DLIGHT_SAV, | ||
- | At 2 a.m on March 11th, you will run the UTC$TIME_SETUP.COM, | + | After 2 a.m on the appropriate Sunday, you will run the UTC$TIME_SETUP.COM, |
- | | + | which will correct the four SYS$TIMEZONE* logicals, and change the rule |
- | | + | listed in TDF$UTC_STARTUP.COM so that your logicals will be correct after |
- | | + | system |
+ | </ | ||
+ | ==== ALPHA / I64 8.3 ==== | ||
- | ==== ALPHA/I64 8.3 ==== | + | < |
- | + | 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. | + | You can check by looking at your SYS$TIMEZONE_RULE logical. |
- | which Provence your machine is located. | + | |
- | timezones, your timezones may not be correct. | + | |
- | SYS$TIMEZONE_RULE logical. | + | |
" | " | ||
then you are operational. | then you are operational. | ||
- | of VMS83A_TZ-V0100 or VMS83I_TZ-V0100 | + | patch of either |
- | + | </code> | |
- | + | ||
- | ==== 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. | ||
+ | </ | ||
+ | |||
+ | The above information is specific to perhaps using the wrong timezone rules for your system. | ||
why_did_time_change_in_the_wrong_month.txt · Last modified: 2019/07/25 03:39 by mmacgregor