HP3000-L Archives

October 1998, Week 2

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Y2K Problem
From:
John Dunlop <[log in to unmask]>
Reply To:
John Dunlop <[log in to unmask]>
Date:
Fri, 9 Oct 1998 16:22:27 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines) 
In article <[log in to unmask]>, Joe Howell
<[log in to unmask]> writes
>The following was observed a few minutes ago by fellow
>contract Y2K Remediators here at NORTEL.
>
>The system clock was set to a few minutes before midnight on
>our test platform. Our group was running a test suite of online
>programs and observing the reaction as the time rolled over past
>midnight.  Alas, all was NOT well, and it was not our code...
[snip]
Roy Brown replied :
>IIRC, the Hardware clock should be at GMT, and the system variable TZ
>adjusts for which TimeZone you are in, exactly.
>
>Can you do a SHOWVAR and see if you have the right TZ for where you are?

It suggests that to me also. It can be checked using
SHOWCLKS.PUBXL.TELESUP if you have this on your system.

Cheers,

John Dunlop

E-mail : [log in to unmask]
Web  : http://homepages.tcp.co.uk/~jdunlop/
"All your HP3000 resources on the Net"

ATOM RSS1 RSS2