Y2k

Tick, Tick, Tick. The Year 2000 draws closer with every passing second. Many have nothing to fear. Why should they. It sounds ridiculous, being afraid of a year, what could possibly go wrong. The truth is, that many things can happen, not from the year itself, but from a simple programming shortcut to save what was once invaluable memory. People say that they do not need computers to live. But then again, many do not realize how much we depend on computers in our lives today. When one goes to the ATM to get money for food, he or she is using computers. When someone starts up their car, they are using computers. When one calls another on the telephone, they are using computers. People use computers more then they think, and when the computers turn back against them, no one really knows what may happen. When the Year 2000 comes, many of these machines will look at the new year as the year 1900. Why. Because back when programmers were setting up the dating system for the original computers, they chose to just use the last two digits of the year to save space; and back then, every byte counted. Called the Y2K problem, this computer glitch could cause some major headaches. The truth is, time is running out, it will take an enormous amount of work to fix, and if we do not fix Y2K in time, everyone s lives will be affected. The Y2K problem isn t just a minor inconvenience. It s a ticking time bomb.

Is there really enough time to fix this potential disaster. Nobody really knows the answer to this question. It is possible that 50% of all the companies that will need to make changes will not be ready in time. (Famighetti, 12) The year 2000 is only about a year away, and a year is not a very long time for a problem this diverse and complex. Problems resulting from the Y2K bug have already started. Forty-four percent of the companies in the United States have already experienced a year 2000 failure. (Stanglin, 45) In 1992, 104 year old Mary Bandar of Winona, Minnesota was invited to join kindergarten classes when her name came up in a search form for people born in the year 1988. (Jager, 14) The computer system running this search was affected by the bug, and thought this lady was four years old. The computer system was never programmed to know the difference between the year 1988 and 1888; it just looked at the date as 88. A similar problem happened to C.G Bloget, who s auto-insurance premium tripled when he was reclassified after his 101st birthday as a high-risk youthful driver. (Jager, 14) These are just two examples of some minor obstacles; the real worry is the major problems, and the government has its share of problems when it comes to Y2K. A recent survey of 44 major airlines revealed that only 67 percent expect their systems to be fully Y2K compliant by Oct. 1, 1999. (Stanglin, 46) That is not a large percentage when you are considering an industry as big as the airplane industry; they transport millions of people everyday. Another industry slow to recognize the problem is the health care industry. (Dash, 24) This one industry can not be forsaken. People can not just forget about the health industry, people s lives are at stake. One more example is the Global Command Control system of the Pentagon. For being one of the most high-tech places around, one would imagine no problems here. Yet in the summer of 1997, the system failed a year 2000 readiness test. (Stanglin, 47) Even with all these problems, the government may not be the worst off. According to Howard Gleckman from Business Week magazine, small businesses could face the worst woes. (Gleckman, 120) All it takes is one lawsuit to put a small company out of business. Time is running out, and we only have a year to fix Y2K. Is that enough time. This thought races across many people s minds. Will we be ready. Only time will tell.

Solving Y2K is a very difficult, expensive, and time-consuming task. No one has yet devised a silver bullet to attack the problem, a nifty program that would search out and convert every date field in a computer s Operating System or software. (Broder) What this means is there are no computer programs made that can fix it all. There are no programs made that can automatically rewrite ever date area in the computer code of a computer s software to be year 2000 compliant. Computer code is what tells the computer program how to run. The worst part is, computer code is not just in one language, just like there are different spoken languages, there are different computer languages. This makes it very difficult to read, and hard to find the people to read it. It is like having a book that randomly jumps from English, to Spanish, to Japanese, and then German. It would be very difficult to read, and you would need many people to accomplish the task. In a computer to fix the problem you must examine every line of code in every computer, locate the instructions regarding dates, and rewrite them to accept 2000 as a year designation. (Stanglin, 46) This seems hard, but it gets worse. Cost is a major issue in fixing Y2K. Nobody is sure how much it will cost, but most think it will cost around $600 billion. (Famighetti, 12) Then there is the problem of all the money spent on litigation. Some estimates say that for every dollar spent on fixing the problem, 2-3 dollars will be spent on litigation. (DeJesus, 55) That is over 1 trillion dollars spent just over lawsuits. So will the common folk have to pay a lot of m