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...
>
>At 1 second before "test midnight", the application was executed,
>and all was well, including the system date and time display in
>the upper corner of the screen.
>
>At 1 second AFTER midnight, the application was again executed,
>and all was NOT well.  The system date still showed 12/31/1999
>and the system time showed (correctly) 00:00:02.  These values
>were obtained using the COBOL 85
>"move function current-date to abc-variable"
>
Sounds like a TZ problem.

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?
--
Roy Brown               Phone : (01684) 291710     Fax : (01684) 291712
Affirm Ltd              Email : [log in to unmask]
The Great Barn, Mill St 'Have nothing on your systems that you do not
TEWKESBURY GL20 5SB (UK) know to be useful, or believe to be beautiful.'