The Y2K Millenium Bug
THE Y2K MILLENNIUM BUG
HON. JOHN LINDER
OF GEORGIA
IN THE HOUSE OF REPRESENTATIVES
Wednesday, January 6, 1999
Mr. LINDER. Mr. Speaker, there are approximately 359 Days, 11 Hours, 32 Minutes, and 26 Seconds until the Year 2000 computer problem affects computers and computer chips worldwide on the morning of January 1, 2000.
As we know, many computers will be unable to process dates beyond December 31, 1999, making the year 2000 indistinguishable from the year 1900. The potential technological turmoil could cause computers to generate incorrect data or stop running. Credit cards, ATM cards, security systems, hospital equipment, telephone service, electricity, and paycheck systems could be affected. I don't think anyone is sure what will happen.
Fortunately, in the year 2000, we have a few days to recover after the Y2K problem hits because January 1st falls on Saturday. However, we lose one potential additional day because the New Year's Day holiday—by law—must be observed on the previous Friday, December 31, 1999.
I have re-introduced legislation that will provide the public and technology professionals with an additional day, prior to the start of the first workweek in January 2000, to work on repairs on failed computer systems caused by the Year 2000 computer problem. My proposal will move the New Year's Day holiday in the year 2000 to Monday, January 3, 2000.
Mr. Speaker, congressional committees have been successfully working to prepare the nation for Y2K, and this is just another proposal that may help ease the difficulties we face. It is not a silver bullet to solve the problem. It is vital that all businesses and government agencies continue to mobilize and work to repair computers in the remaining 359 days before the Y2K problem strikes. This proposal simply ensures that businesses, the public and computer experts have an additional 24 hours to respond to problems that may arise.
This work is in the public domain in the United States because it is a work of the United States federal government (see 17 U.S.C. 105).
Public domainPublic domainfalsefalse