BIND Logfile timestamps

[Trace Trembath]

I have systems running OpenVMS 7.2-1 and TCP/IP services V5.1 ECO5.

The time stamp in the sys$specific:[tcpip$bind]tcpip$bind_run.log file is one hour behind the time when I do a show time at the $prompt.

When I look at the UTC time differential I get the following.

SYSTEM TIME DIFFERENTIAL FACTOR = -6:00 (-21600 seconds).
LOCAL SYSTEM TIME = 27-JAN-2005 09:05:23.48.

We are in Mountain time zone and are currently running in daylight savings mode (testing purposes).

So it looks to me like we are in daylight savings as far as the system is concerned, but in standard time as far as TCP/IP is concerned. Does anyone know how this could be? Is there something I have to do in TCP/IP to ensure that these two times (system and TCP/IP) match up?

This time difference is causing my BIND zone files to be "time warped".

Many thanks for all help and replies.

Trace Trembath

[Ian Miller.]

if you configure the timezone in TCPIP$CONFIG what does it say?

What's the value of
SHOW LOG *TDF*
SHOW LOG *TZ*

[Trace Trembath]

When I run tcpip$config and choose the timezone option, I get the following:

TCPIP uses timezone information provided by the OpenVMS Operating
System. No additonal timezone configuration is needed for TCPIP
when the operating system is configured correctly.

This section verifies the current OpenVMS timezone configuration.
A warning message (TCPIP-W-) indicates that corrective action should
be taken. TCPIP will appear to operate but components may display
either the wrong time or a time inconsistent with other applications.

%TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found.
-TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change
-TCPIP-I-INFO, is present.
-TCPIP-I-INFO, Further action to ensure TDF change is not necessary.

%TCPIP-I-NORMAL, timezone information verified

Press Return to continue ...

Here are the results of the logical names.

AXP9-SYSTEM>sh log *tdf*

(LNM$PROCESS_TABLE)

(LNM$JOB_810A0A40)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)
%SHOW-S-NOTRAN, no translation for logical name *TDF*
$AXP9-SYSTEM>show log *tz*

(LNM$PROCESS_TABLE)

(LNM$JOB_810A0A40)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

"SYS$TZDIR" = "SYS$SYSROOT:[SYS$ZONEINFO.SYSTEM]"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)
$AXP9-SYSTEM>

I found the following logicals earlier,

AXP9-SYSTEM>sh log *zone*

(LNM$PROCESS_TABLE)

(LNM$JOB_810A0A40)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

"SYS$TIMEZONE_DAYLIGHT_SAVING" = "1"
"SYS$TIMEZONE_DIFFERENTIAL" = "-21600"
"SYS$TIMEZONE_NAME" = "MDT"
"SYS$TIMEZONE_RULE" = "MST7MDT6,M4.1.0/2,M10.5.0/2"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)
$AXP9-SYSTEM>

This seems to confirm to me that the system is running in daylight savings mode, which is as expected. The running of tcpip$config also seemed to confirm that TCPIP is using the system timezone information.

Time zone differential appears to be correct when I run the sys$manager:utc$configure_tdf procedure as follows:

$AXP9-SYSTEM>@sys$manager:utc$configure_tdf


Configuring the Time Differential Factor (TDF)

Enter ? anytime for help

[0] Exit
[1] Set the Time Differential Factor
[2] Display the Time Differential Factor

Please pick an option number [2]:

SYSTEM TIME DIFFERENTIAL FACTOR = -6:00 (-21600 seconds).
LOCAL SYSTEM TIME = 27-JAN-2005 10:36:38.24.



Configuring the Time Differential Factor (TDF)

Enter ? anytime for help

[0] Exit
[1] Set the Time Differential Factor
[2] Display the Time Differential Factor

Please pick an option number [2]:

[Trace Trembath]

I did some further testing and have found the following.

I took a test system and change the month to July. The system is still configured as daylight savings. I did not change the system time.

The time stamps in the tcpip log file are now 1 hour ahead.

So DNS seems to know that it's in daylight savings or not based on the time of year.

Any idea if this is configurable or not and /or where BIND is getting this information?

Thanks.

[Ian Miller. · Accepted solution]

I would guess its using "SYS$TIMEZONE_RULE" = "MST7MDT6,M4.1.0/2,M10.5.0/2" to know when daylight savings time starts and ends

[Trace Trembath]

Do you know how to interpret that rule?

I think I can see Month 4 (April) and Month 10 (October).

Thanks.

Also, I have another system that only shows 1 logical when I do.

$AXP1-SYSTEM>sh log *zone*

(LNM$PROCESS_TABLE)

(LNM$JOB_80D0E440)

(LNM$GROUP_000001)

(LNM$SYSTEM_TABLE)

"SYS$TIMEZONE_DIFFERENTIAL" = "-25200"

(LNM$SYSCLUSTER_TABLE)

(DECW$LOGICAL_NAMES)
$AXP1-SYSTEM>

Any idea why the other 3 logicals wouldn't show up?

Thanks.

[Trace Trembath]

Also, where does that sys$timezone_rule logical come from and can I delete it?

[Volker Halle]

Trace,

time zone information on OpenVMS is being maintained by running @UTC$TIME_SETUP.

The logicals are automatically assigned during startup by either DTSS$UTC_STARTUP.COM or TDF$UTC_STARTUP.COM

The timezone rule syntax is descriebd in the C Run-Time Library Ref Manual in the REF section under the 'tzset' function.

Volker.