OPPapers.com

Y2K Bug

The year 2000 problem could have been completely prevented had some
early people envisioned the degree to which the microprocessor would
change our lives. Surely, no one would have thought that in the early
days of ENIAC that everything from your alarm clock to your car would be
computerized. Even the IT managers of the 80's could not be blamed: The
disk space savings from dropping the two digits of the date over 100
Million Records would represent almost 200 Megabytes! Space requirements
aside, overhead on search times and disk loading/access are also added.
Surely one could have designed a system whereby the program would be
aware of the century, regardless of the data records used. Hindsight is
always 20/20 however, and this was almost never the case.
Regardless where you address the problem from, the year 2000 problem is
a huge, expensive and international one. In many cases it is a problem
lined with doubt as to it's effects. This paper will analyze the various
aspects to the year 2000 problem, classical and software solutions to
the problem, and present the author's ideas on how a systematic approach
to the "millennia virus" can prevent doomsday from becoming a reality
for many information technology managers and their corporations.
What, specifically, is this "millennia virus" to begin with? There has
been much talk about it, and most people know it has something to do
with the date formats and how the computer processes them. How it is
affecting that processing is what the key to implementing a solution is.
There are several forms the "bug" will metamorphose into.
For example: Field / Date Processing
Time based calculations
Hardware failure

"Will all be affected by the problem? "OLD will seem YOUNG, a FEW
moments will seem like an ENTIRE century,...