- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- time went back an hour after reboot
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
тАО04-04-2006 08:41 PM
тАО04-04-2006 08:41 PM
time went back an hour after reboot
After it came back up again, the time was an hour behind.
The time logicals we user are :
"SYS$LOCALTIME" = "SYS$SYSROOT:[SYS$ZONEINFO.SYSTEM]GB-EIRE."
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "1"
"SYS$TIMEZONE_DIFFERENTIAL" = "3600"
"SYS$TIMEZONE_NAME" = "BST"
"SYS$TIMEZONE_RULE" = "GMT0BST-1,M3.4.0/01,M10.5.0/02"
I had to correct the time using "set time".
Would anyone have any ideas what went wrong?
We have never configured DTSS, but I am suspicious that it may have something to do with it.
Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 08:55 PM
тАО04-04-2006 08:55 PM
Re: time went back an hour after reboot
What version of VMS, DECniet, TCPIP ?
What is the result of
@sys$manager:utc$time_setup show
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-04-2006 08:57 PM
тАО04-04-2006 08:57 PM
Re: time went back an hour after reboot
Hi
HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 2
on a AlphaServer DS20 500 MHz running OpenVMS V7.3-2
DTSS is in use and will make changes to/from Daylight Saving Time.
(in time zones that use Daylight Saving Time)
LOCAL TIME ZONE = GB-EIRE -- DAYLIGHT TIME
LOCAL SYSTEM TIME = 5-APR-2006 09:56:29.60 (BST)
TIME DIFFERENTIAL FACTOR = 1:00
TIME ZONE RULE = GMT0BST-1,M3.4.0/01,M10.5.0/02
Change GMT to BST on the Fourth Sunday of March (26-Mar-2006) at 01:00
Change BST to GMT on the Last Sunday of October (29-Oct-2006) at 02:00
Also, I found the following entry in operator.log :
%JBC-W-SYSERROR, SYS$MANAGER:JBC$DST_COMMAND.COM daylight savings time process failed system service error at PC 00011EA0
-JBC-W-NOTIMZONRUL, SYS$TIMEZONE_RULE logical not defined, Daylight Savings Time clock adjustments are not possible
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 12:02 AM
тАО04-05-2006 12:02 AM
Re: time went back an hour after reboot
You say the system time went back after reboot... so
Can you check timezone parameter stored in the sysman startup database.
$ mc sysman startup show file UTC$CONFIGURE_TDF.COM /par
parameters to this file
P1: SET and P2:60 shoule be set properly.
regards
Raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 12:09 AM
тАО04-05-2006 12:09 AM
Re: time went back an hour after reboot
This has happened to me many times in the past.
If you read the documentation for SET TIME there is a bit that is critical that often gets overlooked:
(From the OpenVMS FAQ)
4.1.1.2.3 EXE$GQ_SAVED_HWCLOCK
This cell is used by OpenVMS Alpha to keep track of the last time and date that EXE$GQ_SYSTIME was adjusted. It keeps the same time format as EXE$GQ_SYSTIME. The value in this cell gets updated in memory and on disk, every time EXE$GQ_SYSTIME gets adjusted.
* The system parameters SETTIME and TIMEPROMPTWAIT determine how the system time will be set.
* If SETTIME = 0
then EXE$INIT_HWCLOCK reads the hardware clock to set the system time.
o IF TIMEPROMPTWAIT > 0
THEN the value of TIMEPROMPTWAIT determines how long the user is prompted to enter the time and date. If time expires and no time has been entered the system acts as if TIMEPROMPTWAIT = 0.
o IF TIMEPROMPTWAIT = 0
THEN the system time is calculated from the contents of EXE$GQ_SAVED_HWCLOCK + 1.
o IF TIMEPROMPTWAIT < 0
THEN the user is prompted for the time and date and unable to continue until the information is entered.
Unlike the VAX, the Alpha hardware clock tracks the full date and time, not just the time of year. This means it is possible to boot from the CD-ROM media without entering the time at the CD-ROM bootstrap. (This provided that the time and date have been initialized, of course.)
IA-64 (Itanium) hardware time-keeping details to be added...
4.1.1.3 Why does VAX need a SET TIME at least once a year?
Because the VAX Time Of Year (TOY) has a resolution of 497 days, the VAX system time is stored using both the TOY and the OpenVMS VAX system image SYS.EXE. Because of the use of the combination of the TOY and SYS.EXE, you need to issue a SET TIME command (with the time parameter specified) at least once between January 1st and about April 11th of each year, and whenever you change system images (due to booting another OpenVMS VAX system, booting the standalone BACKUP image, an ECO that replaces SYS.EXE, etc).
The SET TIME command (with the current time as a parameter) is automatically issued during various standard OpenVMS procedures such as SHUTDOWN, and it can also obviously be issued directly by a suitably privileged user. Issuing the SET TIME command (with a parameter) resets the value stored in the TOY, and (if necessary) also updates the portion of the time (the current year) saved in the SYS.EXE system image.
This VAX TOY limit is the reason why OpenVMS VAX installation kits and standalone BACKUP explicitly prompt for the time during bootstrap, and why the time value can "get weird" if the system crashes outside the 497 day window (if no SET TIME was issued to update the saved values), and why the time value can "get weird" if a different SYS$SYSTEM:SYS.EXE is used (alternate system disk, standalone BACKUP, etc).
4.1.2 How does OpenVMS VAX maintain system time?
VAX systems maintain an interval clock, and a hardware clock.
The VAX hardware clock is called the TOY ("Time Of Year") clock. The register associated with the clock is called the TODR ("Time Of Day Register").
The TOY clock---as used---stores time relative to January first of the current year, starting at at 00:00:00.00. It is a 100 Hz, 32-bit counter, incremented every 10ms, and thus has a capacity of circa 497 days.
OpenVMS (on the VAX platform) stores system date information---and in particular, the current year---in the system image, SYS$SYSTEM:SYS.EXE.
The TOY is used, in conjunction with the base date that is stored and retrieved from the system image, to initialize the interval clock value that is stored in EXE$GQ_SYSTIME.
Once the interval clock is loaded into the running system as part of the system bootstrap, the system does not typically reference the TOY again, unless a SET TIME (with no parameters) is issued. The interval clock value is updated by a periodic IPL22 or IPL24 (depending on the specific implementation) interrupt. (When these interrupts are blocked as a result of the activity of higher-IPL code---such as extensive driver interrupt activity or a hardware error or a correctable (soft) memory error---the clock will "loose" time, and the time value reported to the user with appear to have slowed down.)
When SET TIME is issued with no parameters, the TOY clock is loaded into the system clock; the running system clock is set to the time stored in the TOY clock. This assumes the TOY clock is more accurate than the system clock, as is normally the case.
On most (all?) VAX systems, the battery that is associated with the TOY clock can be disconnected and replaced if (when) it fails
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 12:49 AM
тАО04-05-2006 12:49 AM
Re: time went back an hour after reboot
HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 2
on a AlphaServer DS20 500 MHz running OpenVMS V7.3-2
mc sysman startup show file UTC$CONFIGURE_TDF.COM /par
%SYSMAN-I-NODERR, error returned from node ALFAT0
-STARTUP-E-FILNOTFND, STARTUP file UTC$CONFIGURE_TDF.COM not found
What sets the time during startup?
What sets the logicals during startup (they do not appear in sylogicals.com)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 12:51 AM
тАО04-05-2006 12:51 AM
Re: time went back an hour after reboot
$ mc sysman startup show file UTC$CONFIGURE_TDF.COM /par
This procedure is obsolete and should not be used anymore ! Timezone changes should only be done by using SYS$MANAGER:UTC$TIME_SETUP.COM, which will put the correct information into SYS$MANAGER:{DTSS|TDF}$UTC_STARTUP.COM
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 01:08 AM
тАО04-05-2006 01:08 AM
Re: time went back an hour after reboot
VMS$BASEENVIRON-050_VMS.COM calls TDF$UTC_STARTUP.COM, if DTSS is not in use. Otherwise DTSS$UTC_STARTUP.COM is called (from NET$STARTUP.COM).
Either one of these 2 procedures is called during startup to set the timezone logicals. The timezone information in these procedures is maintained by @UTC$TIME_SETUP - the ONLY procedure to be used to modify timezone related information.
I assume that this is a standalone node, otherwise it would've got the correct time from another member in the cluster.
During startup, the time must be obtained from the HWCLOCK. If that clock did NOT get updated after the change to BST, this may explain, why the system came up one hour behind the correct time.
I've started using
$ SET AUDIT/ALARM/ENABLE=TIME
$ SET AUDIT/AUDIT/ENABLE=TIME
on our systems to be able to tell, when and by whom the system clock has been changed.
You can look at the last time written to the HWLOCK with ANA/SYS
SDA> EXA/TIME EXE$GQ_SAVED_HWCLOCK
But it may now be too late to find out, why the system came up with a bad time.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 03:36 AM
тАО04-05-2006 03:36 AM
Re: time went back an hour after reboot
I've checked a couple of V7.3-2 systems running DTSS and their EXE$GQ_SAVED_HWCLOCK value was 26-MAR-2006 03:00 (the time we switched to during the MET to MEST DST time change on the last sunday in March).
If - for whatever reason - DTSS failed to correctly update the HWCLOCK on your system, this may explain the behaviour you've seen. The $SET TIME="''f$time()'" in SHUTDOWN.COM would not work if DTSS is still enabled during shutdown.
Did you correctly and cleanly shut down the system ?
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2006 03:38 AM
тАО04-05-2006 03:38 AM
Re: time went back an hour after reboot
We dont use DTSS
The server was rebooted cleanly