We're planning the same.

We will do it on an empty CPU (lucky we are: we will have one).
We will create a SLT (with Config group etc.) and Fullbackup, checking the
tapes etc,
then install the applications accounts from fullbackups from the other CPU,
then hardboot to different dates and running through this famous dates
(31DEC99 to 01JAN00 etc.), in parallell to applications activities etc.
Finally we will do an INSTALL to make sure that we are really back in this
Century for all files.

Such a plan will not risk anything. Some system files will get new dates,
and finally without a complete RESTORE;NOKEEP;OLDDATE you will fall into
some system traps ...

And I assume that a weekend is too short to perform all the magic time
steps ...

Best regards, Andreas Schmidt, CSC, Germany





[log in to unmask] on 12/17/98 05:19:47 PM

Please respond to [log in to unmask]

To:   [log in to unmask]
cc:    (bcc: Andreas Schmidt/HI/CSC)
Subject:  Year 2000 Test




We have converted our data and applications to accomodate 8 digit dates.
We tested with Time Machine and Time Shift and everything is performing
normally.   Our customer has asked us to perform a 'real' simulation by
booting the system with a date in the year 2000 and then testing system and
application software.  Has anyone done this before?  I know we have to be
concerned with software licensing since some of the software licenses
require annual renewal.  Are there issues we need to be concerned with when
we roll back the system to the current date.  Does anyone have a project
plan with which they have done this?   We plan on taking an entire weekend
to roll forward, test and then roll back.  Is this enough time?  Thanks in
advance for anyone's help.
Chris Enderle
IBM Global Services
Voice - 614/251-7186
Fax     - 614/251-7048