- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- pathworks time not moving to DST
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
тАО03-12-2007 11:35 AM
тАО03-12-2007 11:35 AM
pathworks time not moving to DST
using utc$time_setup.com. The system time
moved aok, logicals look ok. we then shutdown
and brought pathworks back up, but pathworks
won't take the new time. we tried several
iterations, no luck. anyone know why it ignores the system clock? the pathworks
book says it is supposed to pick it up ?
tx if any help Dean
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2007 08:06 PM
тАО03-12-2007 08:06 PM
Re: pathworks time not moving to DST
It has been a few years since I touched Pathworks, but I checked the manual and with V7.* it does seem that Pathworks should just take the new system timezone settings after a restart. All I could suggest is re-check your logicals. If all is ok then I would log a call with HP, assuming you have a support agreement.
Failing that, you might want to post some more details, versions etc. Also, are you running the timesource service? perhaps you could post the info from your lanman.ini file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 03:28 AM
тАО03-13-2007 03:28 AM
Re: pathworks time not moving to DST
tx for the reply. we are actually
in az where the time doesn't move, however since we saw it in the field, I reproduced it here. the systems logicals are
"SYS$LOCALTIME" = "SYS$SYSROOT:[SYS$ZONEINFO.SYSTEM.US]MOUNTAIN."
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "1"
"SYS$TIMEZONE_DIFFERENTIAL" = "-21600"
"SYS$TIMEZONE_NAME" = "MST"
"SYS$TIMEZONE_RULE" = "MST7"
eg local time
ENGDS2::MCGORRILL 09:20:27 (DCL)
then a net time from a PC
C:\>net time \\engds2
Current time at \\engds2 is 2/13/2007 8:21 AM
it should have moved.
a look at the pathworks pathworks logs shows
its still back on MST.
12-MAR-2007 17:03:55.08 20402253:007325C0 GMTinit: timezone = 25200
any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 04:22 AM
тАО03-13-2007 04:22 AM
Re: pathworks time not moving to DST
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 04:34 AM
тАО03-13-2007 04:34 AM
Re: pathworks time not moving to DST
$ ucx show conf time
If wrong then try setting the correct values
$ UCX SET CONFIG TIME "xxx"
$ UCX GENERATE TIME
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 05:58 AM
тАО03-13-2007 05:58 AM
Re: pathworks time not moving to DST
you may be on to something, from the log..
13-MAR-2007 10:36:29.31 2040272A:007325C0 Using OpenVMS V7 DEC C time logicals <<<
13-MAR-2007 10:36:29.32 2040272A:007325C0 GMTinit: timezone = 25200
I don't see any logicals. Anyway, I see
now its behavior is, if daylight savings
is set, pathworks takes the system time
and subtracts an hour! thus if my alpha
is at 11am, pathworks offers 10am. why
would it do that?
ucx, we're using tcpip which doesn't use config time anymore..
TCPIP> sho conf time
TIME configuration
Value: not defined
Differential: not defined
PLEASE NOTE WELL:
These values are from the configuration DB but are not actually used by TCPIP.
TCPIP uses the system service SYS$GETUTC() to find the
timezone differential information used by the operating system.
Setting and showing this information is described in the
OpenVMS System Management documentation.
This command is supplied for minimal compatability with UCX command files.
Use of this command is currently depricated. This command may be removed
in a future version of TCPIP.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 06:41 AM
тАО03-13-2007 06:41 AM
Re: pathworks time not moving to DST
>"SYS$TIMEZONE_DIFFERENTIAL" = "-21600"
>"SYS$TIMEZONE_NAME" = "MST"
>"SYS$TIMEZONE_RULE" = "MST7"
Wonder if this might be a concern.
The TIMEZONE_DIFFERENTIAL of -21600 listed above does not match the TIMEZONE_RULE of MST7.
MST7 should = -24200
I checked our Advanced Server here ( vms 7.3-2/Adv. Serv. v 7.3B) and the time was OK.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 08:35 AM
тАО03-13-2007 08:35 AM
Re: pathworks time not moving to DST
Oops. Make that -25200
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 08:44 AM
тАО03-13-2007 08:44 AM
Re: pathworks time not moving to DST
you may be right. I took what utc$time_setup calculated which for this test was -6
6*3600=-21600. I thought maybe it was rules for the crtl. I'd tested that by moving
the vms time ahead a few months, so we'd know we were in what was DST. pathworks still removed an hour.
One fix is to run utc$time_setup and enable
daylight savings and but add an extra -TDF hour to what utc$time_setup calculates. making it -7 instead of -6 pathworks offers time matching the system. Or run utc$time_setup, set for no daylight savings, then it calculates -7 anyway. pathworks offers time matching the system as well. so if it has to be 25200, why did
utc$time_setup calculate -6 (21600)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-13-2007 09:18 AM
тАО03-13-2007 09:18 AM
Re: pathworks time not moving to DST
I haven't seen any details on the OpenVMS version posted, which in conjunction with the discussion here would lead me to assume it isn't V7.3-2 or one of the other supported releases.
Fixing this is several steps, depending on the version and the installed products. I've posted a list of the wrinkles I know about over at http://64.223.189.234/node/72
On the plus side, this error will probably fix itself in about three weeks or so. :-)
Stephen Hoffman
HoffmanLabs