RE: F35 - Y2K

[Lorne Sturgeoff <lgs@xxxxxxxxxxx>]

Be careful!  These things have a way of coming back to bite you (the "you 
tickle it here, it laughs at you over there" syndrome.)  Any date-sensitive 
routines, interest calculations, for example could corrupt your data.  Unless 
you are _very_ familiar with your applications and absolutely confident there 
are no risks, I would strongly opt for the backup/restore.  By the way, tapes 
can fail.  Better to have at least two copies.

-----Original Message-----
From:   nevillekingdom@bardaust.com.au [SMTP:nevillekingdom@bardaust.com.au]
Sent:   Monday, August 10, 1998 8:37 PM
To:     MIDRANGE-L@midrange.com
Subject:        F35 - Y2K


We have an F35 CISC box and would like to set the system date to beyond 2000 as
part of our testing.
As this would be a controlled test no users would be on the system. Journaling,
Job Schedulers, Performance Monitors and user access would all be disabled.

I have read an article in Midrange Computing  Feb 1998 by Ted Holt that states a
full system backup should be taken and when the date is set back to current that
a full restore must be performed. We are not doing an IPL and this restore seems
a little extreme every time we want to do live testing with our test
environment.

Does anyone have any experience or suggestions with the system date or on having
to do a full restore 

Neville Kingdom,
Bard Australia
nevillekingdom@bardaust.com.au

application/ms-tnef