Topic 7 of 29: Y2K or Year 2000 problem
Sat, May 2, 1998 (09:22) |
Paul Terry Walhus (terry)
The Year 2000 Problem or the Y2K Problem.
Is it getting too late for some to do anything? What will be the
consequences?
2 responses total.
Topic 7 of 29 [computer]: Y2K or Year 2000 problem
Response 1 of 2: Paul Terry Walhus (terry) * Sat, May 2, 1998 (09:22) * 22 lines
Some of the best observations I have heard are from cybrcync@well.com
Any company with, say, one or more mainframes or 50+ PCs hooked up to
some servers had better be hustling by now.
We're down to 20 months. 600 days plus change. Any way you look at
it, the schedule is starting to look tight.
Here are some typical steps in a Y2K project, all of which must be
done within 20 months.
Complete Inventory of Hardware/Software.
Replacement of machines that may cause problems.
Replacement of potentially troublesome operating-system software.
Replacement of potentially troublesome standard office software.
Use available software to fix existing databases.
Use available software to fix ~80% of custom applications.
Hire programmers to fix remaining ~20%.
Test.
Need to check how prepared customers and vendors will be.
I think you are going to need a lot of coffee....
Topic 7 of 29 [computer]: Y2K or Year 2000 problem
Response 2 of 2: Paul Terry Walhus (terry) * Sun, Oct 11, 1998 (10:31) * 1 lines
computer conference 
Main Menu