- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- DST Scripting in a Cluster
Operating System - OpenVMS
1753962
Members
7756
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО03-04-2009 10:50 AM
тАО03-04-2009 10:50 AM
We have a standalone node where DST change is handled manually. The script we've used for years by our operators does the following:
...
$ UTC$CONFIGURE_TDF := -
$SYS$SYSTEM:UTC$CONFIGURE_TDF.EXE
$ UTC$CONFIGURE_TDF "SET" "-420" "+60" -
"SYS$COMMON:" ""
$ (restart NTP here)
...
My question is: this year we also need to do the change manually on a 2-node cluster. Can the operators simply run the script on each cluster node, or should I script SYSMAN to do both cluster nodes simultaneously? TIA
...
$ UTC$CONFIGURE_TDF := -
$SYS$SYSTEM:UTC$CONFIGURE_TDF.EXE
$ UTC$CONFIGURE_TDF "SET" "-420" "+60" -
"SYS$COMMON:" ""
$ (restart NTP here)
...
My question is: this year we also need to do the change manually on a 2-node cluster. Can the operators simply run the script on each cluster node, or should I script SYSMAN to do both cluster nodes simultaneously? TIA
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 11:28 AM
тАО03-04-2009 11:28 AM
Solution
What OpenVMS version, and is it matched to current?
Current versions generally deal with this stuff correctly, and automatically.
Changing the times simultaneously or near-simultaneously isn't a big difference; if the boxes derail or the times are skewed, it's usually due to something (else) that happens during the change-over. (Like CMS access, for instance, or batch job that are kicking off; those can get into trouble during a cluster time skew.) So yes, better to have the changes occur closer together.
I'd tend to use the provided DAYLIGHT_SAVINGS.COM (sic) command procedure, or use the UTC$TIME_SETUP.COM procedure to make the change. Going directly after the underlying pieces isn't usually a good idea. (Unless HP has changed how this stuff works, and is now recommending this approach.)
Or you can forget this particular idea (DST) and move the box to UTC, and leave it there permanently.
http://64.223.189.234/node/72
Current versions generally deal with this stuff correctly, and automatically.
Changing the times simultaneously or near-simultaneously isn't a big difference; if the boxes derail or the times are skewed, it's usually due to something (else) that happens during the change-over. (Like CMS access, for instance, or batch job that are kicking off; those can get into trouble during a cluster time skew.) So yes, better to have the changes occur closer together.
I'd tend to use the provided DAYLIGHT_SAVINGS.COM (sic) command procedure, or use the UTC$TIME_SETUP.COM procedure to make the change. Going directly after the underlying pieces isn't usually a good idea. (Unless HP has changed how this stuff works, and is now recommending this approach.)
Or you can forget this particular idea (DST) and move the box to UTC, and leave it there permanently.
http://64.223.189.234/node/72
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 11:55 AM
тАО03-04-2009 11:55 AM
Re: DST Scripting in a Cluster
Looks like the HP supplied script is better than mine ;) so we'll use it. Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2009 12:16 PM
тАО03-04-2009 12:16 PM
Re: DST Scripting in a Cluster
Make *sure* you're patched to current for whatever release is in use, as there *have* been bugs here. And it would not surprise me that there are *still* bugs here.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP