- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DST$CHANGE issue/observation.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 04:55 AM
тАО11-02-2009 04:55 AM
DST$CHANGE issue/observation.
First I ran SYS$EXAMPLES:DAYLIGHT_SAVINGS.COM to generate SYS$MANAGER:DST$CHANGE.COM. Then,
On each of my systems I waited until after 02:00am DST, then ran SYS$MANAGER:DST$CHANGE. On each of my systems the result was the same, vis. the time was changed, but the logicals were not.
Checking the code in DST$CHANGE, it basically seems to execute
utc$time_setup "" "TDF"
followed by
utc$time_setup "" "RULE"
"TDF" should reset the logical SYS$TIMEZONE_DIFFERENTIAL, which it didn't do, and
"RULE" should reset the logical SYS$TIMEZONE_RULE, which it may have done, (I think that the initial string may "EST5EDT4" may have been reversed.)
The interesting thing is that waiting until after 2:00 am EST, and then running utc$time_setup "" "RULE" again, successfully resets all of the logicals. (I determined this on a test system by manually setting the time back forward after running DST$CHANGE, and then manually setting the time back after running utc$time_setup "" "RULE" again.) This seems to resolve the problem.
So the process looks like this; After 2am DST,
$ @TCPIP$NTP_SHUTDOWN ! do this to avoid complications.
$ @DST$CHANGE ! time is set back 1 hour to 1am EST, logicals not reset
$ set time="+1:00:00"
$ @utc$time_setup "" "RULE" ! sets the logicals correctly.
$ set time="-1:00:00" ! Back to EST.
later, @TCPIP$NTP_STARTUP
After completing this process I get;
$ @sys$manager:utc$time_setup "" "SHOW"
: : : :
LOCAL TIME ZONE = US / EASTERN -- STANDARD TIME
LOCAL SYSTEM TIME = 2-NOV-2009 07:47:44.41 (EST)
TIME DIFFERENTIAL FACTOR = -5:00
TIME ZONE RULE = EST5EDT4,M3.2.0/02,M11.1.0/02
Change EST to EDT on the Second Sunday of March (8-Mar-2009) at 02:00
Change EDT to EST on the First Sunday of November (1-Nov-2009) at 02:00
and
$ show log sys*time*
(LNM$SYSTEM_TABLE)
"SYS$LOCALTIME" = "SYS$SYSROOT:[SYS$ZONEINFO.SYSTEM.US]EASTERN."
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
"SYS$TIMEZONE_DIFFERENTIAL" = "-18000"
"SYS$TIMEZONE_NAME" = "EST"
"SYS$TIMEZONE_RULE" = "EST5EDT4,M3.2.0/02,M11.1.0/02"
Having read through the DAYLIGHT_SAVINGS script, I am currious as to whether I would be better off just running
utc$time_setup "" "ALL"
Any Comments.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 05:05 AM
тАО11-02-2009 05:05 AM
Re: DST$CHANGE issue/observation.
I dont recall having this problem back in March when the clocks went forward. It may only be a problem when the clocks go back!
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 09:50 AM
тАО11-02-2009 09:50 AM
Re: DST$CHANGE issue/observation.
However, on our two standby nodes (used for disaster recovery), I apparently had not correctly enabled time zone changes so I had to go back and do those by hand. On followup, it was probably because DTSS$CLERK was not running on those two boxes.
Interestingly enough, NONE of the systems in question had SYSGEN parameter AUTO_DLIGHT_SAV set to 1. So that means I have some other logical name missing on our standby systems, and that parameter isn't required for the change if DTSS$CLERK is running. At least, that's the way I interpret what I see.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 09:58 AM
тАО11-02-2009 09:58 AM
Re: DST$CHANGE issue/observation.
What you say is correct. If DTSS is running (i.e. you have the DTSS$CLERK process running, then the timechange occurs automatically, including (from what you say) the logicals getting re-defined. The same is true (I assume) if the system parameter AUTO_DLIGHT_SAV is set to 1.
In our case, it would be potentially disasterous if the time was set back 1 hour while our in-house apps were running, so we prefer to keep full control over the process. This is why we depend on the DST$CHANGE script.
I am more concerned by the fact that the script did not perform as advertised (at lease by my understanding).
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2009 10:21 AM
тАО11-02-2009 10:21 AM
Re: DST$CHANGE issue/observation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2009 01:07 PM
тАО11-04-2009 01:07 PM
Re: DST$CHANGE issue/observation.
my guess is, the code (or just logic in general) does not know, when in that magic hour between 1am and 2am, if the transition has taken place or not ... so things just do not work right until after the second 2am.
My solution (rather poor) is to simply wait until after the second 2am to do RULE (for me that sometimes means just sitting around the office for an hour in the middle of the night :-) ).
Verne Britton
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2009 04:09 AM
тАО11-05-2009 04:09 AM
Re: DST$CHANGE issue/observation.
Dave.