- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Daylight Savings Time Change
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
тАО10-14-2003 11:07 AM
тАО10-14-2003 11:07 AM
Daylight Savings Time Change
.
1. Stop DTSS
2. Run a program that will slow the clock down by adjusting the EXE$GL_TICKLENGTH and EXE$GL_TIMEADJUST system data cells.
After 2:00am (3:00am if no time change was performed)
3. Run DTSS$SET_TIMEZONE INITIALIZE
4. Start DTSS
At this point when DTSS was started the time on the system was 2:20am. After DTSS started it set all the clocks back to 1:20am├в a second fallback.
.
This year we will add the following before starting DTSS:
3.5 run UTC$CONFIGURE_TDF SET -420 "" "" NOSETTIME
.
Any GURU out there knows for sure that this will do the trick?
.
Thanks for input,
...Mi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 12:58 PM
тАО10-14-2003 12:58 PM
Re: Daylight Savings Time Change
Not 100% positive here, but in my old procedures I note that we used DTSS$SET_TIMEZONE MODIFY to change the timezone on the running systems. Since we switched to an NTP time server, we have DTSS turned off.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 01:56 PM
тАО10-14-2003 01:56 PM
Re: Daylight Savings Time Change
http://h71000.www7.hp.com/wizard/wiz_8589.html
DTSS should be DST aware as of OpenVMS 7.3.
I personally use NTP too and have AUTO_DLIGHT_SAV enabled, so no first hand experience with DTSS.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-14-2003 10:00 PM
тАО10-14-2003 10:00 PM
Re: Daylight Savings Time Change
This sort of thing is needed.
$ UCX SET CONFIG TIME "GMT0 BST1,3.26.0/2,10.31.0/2"
$ UCX GENERATE TIME
For TCPWARE
NETCU SET TIMEZONE BST
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2003 09:10 AM
тАО10-21-2003 09:10 AM
Re: Daylight Savings Time Change
$! Set EXE$GQ_TDF data cell to correct
$! value, update SYS$TIMEZONE.DAT
$ MCR UTC$CONFIGURE_TDF.EXE SET -420 "" "" ""
$
$! Update all sys$timezone logicals, update
$! DTSS$TIMEZONE_DIFFERENTIAL.DAT. This
$! image will verify the need to update the
$! system time if EXE$GQ_TDF is not the new
$! timezone value.
$ MCR DTSS$SET_TIMEZONE /VERBOSE MODIFY
...Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2003 09:49 PM
тАО10-30-2003 09:49 PM
Re: Daylight Savings Time Change
One of my customers reported a problem due to _switching_ time backward (all times AM, automaticly recorded (= system time...))
An incident was reported at 2:30, a unit reported "on location" at 2:40, and reported free 3:15 (summertime) - but since time changes at 3:00 over here, the recorded time was 2:15. All times stored as generated.
This causes trouble, of course, when these times are passed to other systems (as we found out) or are being analysed (this incident for instance has a NEGATIVE duration).
_Swtiching_ the clock foreward is less problematic but could impose similar problems.
What would be the best (or less worse) solution here? Full overhaul of the whole system is out of the question (it concerns a number of (loosely coupled) applications), nor stopping the systems for an hour...
OpenVMS Developer & System Manager