[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECnet/OSI for OpenVMS |
|
| Moderator: | TUXEDO::FONSECA |
|
| Created: | Thu Feb 21 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3990 |
| Total number of notes: | 19027 |
3912.0. "different "Next TDF Change" display Alpha vs. VAX" by CSC32::J_RYER (MCI Mission Critical Support Team) Thu Mar 27 1997 18:03
My customer is trying to reassure himself that DTSS is going to
correctly handle the daylight savings timeshift, so he's been
closely looking at the dtss NCL characteristics on all his systems.
He has a number of Alpha's, as well as a number of VAXes, all
running OSI V6.2 eco 4. They are all set up for Mountain Time
(current -07:00 offset from UTC, will go to -06:00 when daylight
savings time kicks in).
He has noticed that on the Alpha's the Next TDF Change time shows
as 1997-04-06-03:00:00.000-06:00I0.000, while on the VAXes, it shows
as 1997-04-06-01:59:59.999-07:00I0.000. Now, both of these seem to
translate to the same absolute time (2:00 a.m. Mountain Time), but
he wants to know why the Alpha's are displaying the time in a
format that would be more appropriate for either CST or MDT (rather
than MST, which is what the timezone is set to).
I'll forward below complete ncl>sho dtss all and $sho log sys$timezone*
output, both from an Alpha and a VAX.
Thanks in advance for any comments,
Jane Ryer
MCI Mission Critical Support Team
Here's an Alpha:
CONCS1> mc ncl
NCL>sho dtss all
Node 0 DTSS
at 1997-03-27-15:48:48.119-07:00I13.018
Status
Current Time = 1997-03-27-15:48:48.119-07:00I13.018
Uid = D4DAB59B-9D71-11D0-8007-AA0004008F5E
Last Synchronization = 1997-03-27-15:43:41.280-07:00I12.981
State = On
Characteristics
Error Tolerance = +0-00:10:00.000Iinf
Local Time Differential Factor = -0-07:00:00.000Iinf
Maximum Inaccuracy = +0-00:00:00.200Iinf
Servers Required = 1
Query Attempts = 3
LAN Timeout = +0-00:00:05.000Iinf
WAN Timeout = +0-00:00:15.000Iinf
Synchronization Hold Down = +0-00:10:00.000Iinf
Type = Clerk
Clock Adjustment Rate = 10000000
Maximum Clock Drift Rate = 100000
DNA Version = V1.0.0
DTSS Version = V1.1.0
Time Representation Version = V1.0.0
Global Directory = MCI:.DTSS_GlobalTimeServers
Automatic TDF Change = True
Next TDF Change = 1997-04-06-03:00:00.000-06:00I0.000
Clock Resolution = 976500
Counters
Creation Time = 1997-03-15-20:22:22.009-07:00Iinf
Local Times Not Intersecting = 0
Too Few Servers Detected = 0
Too Many Servers Detected = 0
Protocol Mismatches Detected = 0
Time Representation Mismatches Detected = 0
Invalid Messages Detected = 0
Clock Settings = 1
Time Differential Factor Settings = 0
System Errors Detected = 0
Synchronizations Completed = 1827
Enable Directives Completed = 1
Disable Directives Completed = 0
Insufficient Resources Detected = 0
NCL>sho imp
Node 0
at 1997-03-27-15:49:17.979-07:00I13.021
Characteristics
Implementation =
{
[
Name = OpenVMS AXP ,
Version = "V6.2-1H2"
] ,
[
Name = DECnet/OSI for OpenVMS ,
Version = "DECnet/OSI for OpenVMS Version V6.2-ECO04 7-OCT-1995
18:41
:22.92"
]
}
NCL>exit
CONCS1> sho log sys$timezone*
(LNM$PROCESS_TABLE)
(LNM$JOB_80E646C0)
(LNM$GROUP_000001)
(CONSTANT_LNT)
(DEV_LNT)
(LNM$SYSTEM_TABLE)
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
"SYS$TIMEZONE_DIFFERENTIAL" = "-25200"
"SYS$TIMEZONE_NAME" = "MST"
"SYS$TIMEZONE_RULE" = "MST7MDT6,M4.1.0/2,M10.5.0/2"
(DECW$LOGICAL_NAMES)
CONCS1>
-----------------------------------------------------------------------
And here's the output from a VAX:
$ mc ncl
NCL>sho dtss all
Node 0 DTSS
at 1997-03-27-15:50:55.109-07:00I13.061
Status
Current Time = 1997-03-27-15:50:55.109-07:00I13.061
Uid = BE06AFA0-9D53-11D0-800E-AA000400A35E
Last Synchronization = 1997-03-27-15:44:08.845-07:00I13.035
State = On
Characteristics
Error Tolerance = +0-00:10:00.000Iinf
Local Time Differential Factor = -0-07:00:00.000Iinf
Maximum Inaccuracy = +0-00:00:00.200Iinf
Servers Required = 1
Query Attempts = 3
LAN Timeout = +0-00:00:05.000Iinf
WAN Timeout = +0-00:00:15.000Iinf
Synchronization Hold Down = +0-00:10:00.000Iinf
Type = Clerk
Clock Adjustment Rate = 10000000
Maximum Clock Drift Rate = 100000
DNA Version = V1.0.0
DTSS Version = V2.0.0
Time Representation Version = V1.0.0
Global Directory = MCI:.DTSS_GlobalTimeServers
Automatic TDF Change = True
Next TDF Change = 1997-04-06-01:59:59.999-07:00I0.000
Clock Resolution = 10000000
Counters
Creation Time = 1997-03-15-16:46:58.900-07:00Iinf
Local Times Not Intersecting = 0
Too Few Servers Detected = 0
Too Many Servers Detected = 0
Protocol Mismatches Detected = 0
Time Representation Mismatches Detected = 0
Invalid Messages Detected = 0
Clock Settings = 1
Time Differential Factor Settings = 0
System Errors Detected = 0
Synchronizations Completed = 1847
Enable Directives Completed = 1
Disable Directives Completed = 0
Insufficient Resources Detected = 0
NCL>sho imp
Node 0
at 1997-03-27-15:50:58.179-07:00I13.062
Characteristics
Implementation =
{
[
Name = OpenVMS VAX ,
Version = "V6.1 "
] ,
[
Name = DECnet/OSI for OpenVMS ,
Version = "DECnet/OSI for OpenVMS Version V6.2-ECO04 12-OCT-1995
01:19
:21.01"
]
}
NCL>exit
$ sho log sys$timezone*
(LNM$PROCESS_TABLE)
(LNM$JOB_83552880)
(LNM$GROUP_000001)
(CONSTANT_LNT)
(DEV_LNT)
(LNM$SYSTEM_TABLE)
"SYS$TIMEZONE_DAYLIGHT_SAVING" = "0"
"SYS$TIMEZONE_DIFFERENTIAL" = "-25200"
"SYS$TIMEZONE_NAME" = "MST"
"SYS$TIMEZONE_RULE" = "MST7MDT6,M4.1.0/2,M10.5.0/2"
(DECW$LOGICAL_NAMES)
$
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3912.1 | DTSS is revealing the implementation.... | TWICK::PETTENGILL | mulp | Tue Apr 22 1997 22:24 | 6 |
| The different displayed values are just revealing details of the internal
implementation of the time change logic. Given the complaints and all things
being equal, I'd change the display code to be consistent if I could.
However, I can't.
Save everyone some time; submit an IPMT on this.
|