If you are ABSOLUTELY certain your clocks are OK and this weekend won't be
a big deal, you can probably skip this message. If you just think you're
OK (like I did until today) you might want to read on:
I exchanged a couple of off-list mails with Cynthia Bridges-Fowler yesterday
about setclock and so forth. And today I realized I was wrong (ooops!).
The information is probably useful enough for a public posting, so let me
catch you up...
On Tue, 24 Oct 95 13:26:26 EDT I told Cynthia Bridges-Fowler:
>On Tue, 24 Oct 1995 11:58:35 -0500 you said:
>> [...] Here's what my
>>system clock info looks like. I think I must need to do something to
>>it because it looks messed up to me. Do you have any ideas?
She had sent SHOWCLKS.PUBXL.TELESUP output and SHOWCLOCK results; the
MPE "timezone" was really strange since her system clock was off:
>> *************************************************************
>> *** Greenwich Mean Time : FRI, DEC 30, 1994, 5:00 PM ***
>---This is the real clock time:^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
>> *** GMT/MPE offset : +7145:30:00 ***
>---This is your "timezone" now:^^^^^^^^^^^
>
>> *** MPE System Time : TUE, OCT 24, 1995, 10:30 AM ***
>---Add the two together to get:^^^^^^^^^^^^^^^^^^^^^^^^^^^
To anyone reading, if you haven't looked at a SHOWCLOCK command and/or
run SHOWCLKS.PUBXL.TELESUP on your system, DO IT NOW before the weekend :-)
If you do NOT have a proper system clock setting of GMT and an equally
correct "timezone", you will NOT get the desired results when you change
your timezone with SETCLOCK TIMEZONE=. I explained how to set them up
if they weren't correct already, and concluded the posting with a sample:
>You should have something more like ours:
>
> *************************************************************
> *** Greenwich Mean Time : TUE, OCT 24, 1995, 9:35 AM ***
> *** GMT/MPE offset : +4:00:00 ***
> *** MPE System Time : TUE, OCT 24, 1995, 1:23 PM ***
> *************************************************************
I should practice what I preach, and Cynthia, your system should most
definitely NOT look like mine did yesterday :-) To make matters worse,
I also included showclock results.
>SYSTEM TIME: TUE, OCT 24, 1995, 1:23:58 PM
>CURRENT TIME CORRECTION: 0 SECONDS
>TIME ZONE: 4 HOURS 0 MINUTES EASTERN HEMISPHERE
^^^^^^^^^^^^^^^^^^
Ooops :-) Unless my 960 is running so fast it's breaking the time barrier
we're in the western hemisphere. Aaargh. But to the point at hand. Do
as I say, not as I do :-)
So now I get to play around and find the best way to fix a broken timezone.
The following seems to be the best. Do a SETCLOCK TIMEZONE= to correct the
offset. This will start a gradual clock correction interval, but since you
don't REALLY want to change the current MPE time, do SETCLOCK;CANCEL. This
operation leaves you in a time warp -- the system clock gets shifted a bit
but the timezone is fixed. For example, after the ;CANCEL:
*************************************************************
*** Greenwich Mean Time : WED, OCT 25, 1995, 5:28 AM ***
*** GMT/MPE offset : -4:00:00 ***
*** MPE System Time : WED, OCT 25, 1995, 9:12 AM ***
*************************************************************
while SHOWCLOCK is somewhat misleading (can't see "real" system clock):
SYSTEM TIME: WED, OCT 25, 1995, 9:13:08 AM
CURRENT TIME CORRECTION: 0 SECONDS
TIME ZONE: 4 HOURS 0 MINUTES WESTERN HEMISPHERE
I then followed up with a SETCLOCK DATE=;TIME=;NOW (to set it just slightly
ahead of the real time). This DID fix the real GMT clock, and a final
SETCLOCK CORRECTION= slowed it back down to the "actual" time.
I don't know if the SETCLOCK DATE/TIME;GRADUAL would work or not, given
the state of the clocks and the offset at that point.
"Does Anybody Really Know What Time It Is?"
[\] Jeff Kell <[log in to unmask]>
|
