why_did_time_change_in_the_wrong_month
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
why_did_time_change_in_the_wrong_month [2019/07/25 03:07] – created mmacgregor | why_did_time_change_in_the_wrong_month [2019/07/25 03:28] – 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? ====== | ||
Line 15: | Line 16: | ||
NOTES: | NOTES: | ||
- | If the VMS version is not listed below and you have questions, then log a call with PARSEC and we' | + | 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. | ||
- | ===== 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, | a. Execute immediately, | ||
system startup file: | system startup file: | ||
- | $ DEFINE/ | + | $ DEFINE/ |
- | _$ " | + | |
- | 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 |
- | | + | commands: |
$ INSTALL := $INSTALL | $ INSTALL := $INSTALL | ||
Line 43: | Line 45: | ||
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 ALPTZ01_062 patch on the web. Copy this file to your node, then | + | |
| | ||
| | ||
Line 55: | Line 57: | ||
| | ||
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 81: | Line 84: | ||
system startup file: | system startup file: | ||
- | $ DEFINE/ | + | $ DEFINE/ |
- | _$ " | + | |
b. Then, each future time change, issue the following commands: | b. Then, each future time change, issue the following commands: | ||
Line 90: | Line 92: | ||
$ 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 105: | Line 106: | ||
You will need to find a machine that has already installed the TZ patch. | You will need to find a machine that has already installed the TZ patch. | ||
example, the VMS732_TZ-V0300 or VMS82_TZ-V0200. | example, the VMS732_TZ-V0300 or VMS82_TZ-V0200. | ||
- | 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/ | $ CREATE/ | ||
Line 127: | Line 127: | ||
$ @SYS$MANAGER: | $ @SYS$MANAGER: | ||
- | |||
[5] Configure Timezone Differential Factor | [5] Configure Timezone Differential Factor | ||
Line 133: | Line 132: | ||
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 146: | Line 145: | ||
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, | + | At 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 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 166: | Line 166: | ||
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 179: | Line 179: | ||
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 the US customers, the solution is already built into the OpenVMS codestream, | + | For Canadian customers, it depends on which Provence your machine is located. |
- | treat 2007 the same as you did in 2006. | + | If you are in the Mountain or Pacific timezones, your timezones may not be correct. |
- | which Provence your machine is located. | + | You can check by looking at your SYS$TIMEZONE_RULE logical. |
- | 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 |
+ | </ | ||
- | *** 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