Y2K relegates computers to early fall freeze! Fears of corrupting clean code and the need for final testing are two reasons companies are talking about freezing all computer changes at some point this fall, according to the New York Times. Consultants and companies selling Year 2000 software-testing tools contend that repairs can miss many date problems and introduce bugs. The Gartner Group, a technology consultant in Stamford Conn., says it's common to find errors in 5 percent of computer code that has been altered during Y2K work- and 15 percent in poorly run projects. And normal activites like adding equipment or software carry the risk of inadvertantly introducing bugs into systems that had been cleaned and tested. Take a look at the information on a Power Company, industry watch paper. http://www.pdxweb01.pacificorp.com/Ptoday/990831/ Look under the section Industry Watch.

-- R.J. Renolds (Y2KEYES@open.com), August 31, 1999

Answers

Thanks for the info, the URL didn't work....... :(

-- Kristi (securxsys@cs.com), August 31, 1999.

Look up the Pacificorp web page. Sorry about the url page. The site I posted was on the top of the web page, when I saw the info.

-- R.J.R. (Y2KEYES@open.com), August 31, 1999.

What you have posted here appears to be quite correct. The power company that I work for will freeze all systems from the end of this month. ie. no new computer software or equipment will be installed untill after the roll over. That way we can be sure that we are not importing any new problems which may not be identified in time.

We are almost complete with our remediation, but their is one embedded system which has only recently failed a Y2K test, and which will not be fixed in time. Fortunately we do have a simple work around by turning the clock on this single system by 10 years. It does not interface or network with any other computer system and so changing the date will not cause any major problems.

Malcolm

-- Malcolm Taylor (taylorm@es.co.nz), September 01, 1999.