TCPWARE and SYS$TIMEZONE logicals.

[The Brit]

Q1. Does TCPWARE, and in particular TCPWARE's NTP server, make any use of the VMS SYS$TIMEZONE... Logicals. vis.

"SYS$TIMEZONE_DAYLIGHT_SAVING" = "1"
"SYS$TIMEZONE_DIFFERENTIAL" = "-14400"
"SYS$TIMEZONE_NAME" = "EDT"
"SYS$TIMEZONE_RULE" = "EST5EDT4,M3.2.0/02,M11.1.0/02"

I noticed that the two nodes which I have running TCPWARE, made the transition to EST ok, however the SYS$TIMEZONE Logicals are still set for EDT.

Q2. I would like to run the UTC$TIME_SETUP on these two nodes (without reseting the local time), just to set the logicals names correct. Does anyone see a problem with that.

Dave

[Richard Whalen · Accepted solution]

TCPware does not use the logicals, but the most recent version (5.7) can set the logicals when the time changes if set_vms_logicals is included in the configuration file.

This information is missing from the documentation available on line; the details are:

Causes the NTP server to also adjust the value of the VMS logicals SYS$TIMEZONE_DIFFERENTIAL, SYS$TIMEZONE_DAYLIGHT_SAVING and SYS$TIMEZONE_NAME when it changes the "TCPWARE_TIMEZONE" logical at DST start or end.

NTP does NOT set SYS$TIMEZONE_RULE, which generally does not change. The format of SYS$TIMEZONE_RULE is specified in SYS$MANAGER:UTC$TIME_SETUP.COM

There is also a call_dst_proc option that allows you to have the commands in TCPWARE:NTPD_DST_PROC.COM executed when the time changes.
Where:

â ¢ p1 = Current timezone name - string (e.g. "EST" or "EDT")

â ¢ p2 = Timezone offset in seconds - integer (e.g. "-18000" or "-14400")

â ¢ p3 = DST in effect? - boolean ("Y", "N")

â ¢ p4 = In Twilight Zone? - boolean ("Y", "N")

â ¢ p5 = Startup or DST change? - string ("START" or "DST")