RE: Y2K testing -- MIDRANGE-L


We purchased a dedicated 150 As/400 for all of our application and OS y2k
testing which went on for about 6 months. While this was a luxury we felt it
necessary as changing the dates on an existing dev as/400 would have caused
to many problems with other application environments.

However there are a few points I'd make re changing the dates back & forth:

You will have very messy log files ( qhst, qsysopr, etc. )Also, if you have
a limit on the number of days that joblogs are kept in qezjoblog you will
need to keep an eye on the number of files that build up if you have set a
date far into the future and back again.

I also found that TCP/IP frequently died and the only way to ensure that you
don't run into problems is to stop / start the services after each change or
do an IPL which is probably the safest bet. Other than that, we didn't
experience do many problems.

With regard to your appliactions, you'll need to consider the effects of
conflicting time stamps on your files etc. as you change the dates.

I would not just assume that getting certification on OS/400 is enough.
While the IBM website that has the y2k certification database is very
useful, you need to keep checking the status of
os400 products as y2k problems are found on an ongoing basis.

Regards,

Neil

-----Original Message-----
From: PhaniHR [mailto:PhaniHR@inf.com]
Sent: 17 June 1999 07:33
To: 'MIDRANGE-L@midrange.com'
Subject: Y2K testing


Hi Midrangers,

We are planning to do Y2K testing from the Systems ponit of view. We are
planning to change the System date, do our testing and finally change the
system date back to the original one. I heard that IBM doesn't recommend
changing the System date to back and forth.  I would like to know how others
are going about it OR is it just enough if you are at Y2K ready OS version.

Thanks in advance,
phanihr@inf.com
+---
| 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
+---
**********************************************************************************************
This email and any files transmitted with it are confidential and intended for 
the addressee only. If you have received this information in error, please 
notify the sender or Postmaster@lifetime.ie immediately and delete this email. 
if you  are not the
intended recipient, any distribution or copying of this email is strictly 
prohibited. Any views expressed in this email are those of the individual 
sender unless the sender specifically states otherwise.

This footnote also confirms that this email message has been swept by 
MIMEsweeper for the presence of computer viruses.
**********************************************************************************************
+---
| 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
+---