[Info-vax] satellite one hour ahead

[Phillip Helbig undress to reply]

In article <d8feceff-96a7-467e-a230-80d558b7042e at googlegroups.com>,
mcleanjoh at gmail.com writes: 

> > > I'm wondering about a SET TIME command that might have been added to
> > > correct a time problem when summer time started.
> > 
> > Nope.  Good idea; just checked.
> 
> Nothing at all that's unique?  
> - No MODPARAMS.DAT to set nodename etc. ?

Well, of course, but just the stuff that MUST be different.

> - No software that runs only on that node or has a special
> configuration for that node (e.g. DecWindows)? 

No.

> Have you checked all the LOGIN.COM files for all accounts that are
> used during system boot (sometimes third-party software is started under
> special accounts) 

Yes.

> Also, when do you first see that the time is bad? Is it during the
> booting or is it when the system is accessed by users? 

I'll check that at next boot.  Normally the console isn't switched on 
during boot.

> Throw some $ SHOW TIME commands into the startup - or better yet some
> output that says where it is in the startup + the time (even WRITE
> SYS$OUTPUT "point A - " F$TIME(), then point B ... anything that helps
> you identify where the time was reset. 

$ dir/dat startup.log;

Directory DSA150:[SYS230.SYSEXE]

STARTUP.LOG;543      25-OCT-2016 09:24:34.76

$ sea startup.log; 9:
%STDRV-I-STARTUP, OpenVMS startup begun at 25-OCT-2016 09:24:34.27

%STDRV-I-STRTPHAS, starting phase INITIAL at 25-OCT-2016 09:24:35.40

%STDRV-I-STRTPHAS, starting phase DEVICES at 25-OCT-2016 09:24:51.80
$    WRITE BOOT_HISTORY "25-OCT-2016 09:23:44.00 CALVIN 25-OCT-2016 09:26:10.28 STARTUP"

%STDRV-I-STRTPHAS, starting phase PRECONFIG at 25-OCT-2016 09:26:11.03

%STDRV-I-STRTPHAS, starting phase CONFIG at 25-OCT-2016 09:26:11.09

%STDRV-I-STRTPHAS, starting phase BASEENVIRON at 25-OCT-2016 09:27:04.54

%STDRV-I-STRTPHAS, starting phase LPMAIN at 25-OCT-2016 10:29:06.42

%STDRV-I-STRTPHAS, starting phase LPBETA at 25-OCT-2016 10:29:09.54

%STDRV-I-STRTPHAS, starting phase END at 25-OCT-2016 10:29:09.54

OK, it changes during the startup sequence.

sea startup.log; "16 10:"

%STDRV-I-STRTPHAS, starting phase LPBEGIN at 25-OCT-2016 10:27:06.21
$     write sys$output f$fao("!/!AS","%TCPIP-I-INFO, TCP/IP Services 
startup beg

%TCPIP-I-INFO, TCP/IP Services startup beginning at 25-OCT-2016 10:27:11.17

Many more timestamps an hour at around 10:30, i.e. an hour too late.

OK, searching for the date finds 

%STDRV-I-STRTPHAS, starting phase LPBEGIN at 25-OCT-2016 10:27:06.21

as the first wrong date.  What is before that?

$@SYS$STARTUP:TDF$UTC_STARTUP.COM

So, it looks like nothing I've added, but rather some bug in the time-
zone rules.

I'll see what I can find with SET PREFIX.