Re: Turning back QDATE

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

DANGER!  DANGER, WILL ROBINSON!

I'm assuming you're doing Y2K testing...

The problem, as I understand it, is that you will inevitably and invariably
create something that will have a date beyond Y2K.  This will confuse the
heck out of your software when you return to the present.  Things like
spool files, Performance Manager files, etc. etc. will cause 'unpredictable
results.'

The only way I've heard that this can safely be done on a single machine is to:

        Backup the entire machine.  Twice.

        Crank the date Beyond 2000 and test.

        Wipe out your hard drives.  Totally blank.

        Restore  the system from the backup tapes.

--Paul E Musselman
PaulMmn@ix.netcom.com




>We have just been notified that we need to test some software one of our
>Texas divisions is using to run their business.  The creator of this
>software will not send us a copy to load on a test box.  We have been
>instructed to test it over a weekend (or series of weekends) by turning
>back the date on the Production AS/400 over in Texas.  I have heard
>through this list such a thing is a very, very not good idea.  Now I I
>need some firm reasons or I will find myself participating in this very
>thing.  ANY help is GREATLY appreciated.
>
>Thanks!!!


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---