To: Marji who wrote (6644 ) 7/11/1998 3:08:00 AM From: Tharos Read Replies (2) | Respond to of 17367
So the mysterious Y2K problem rears its ugly head on the Xoma thread. Perhaps I can answer your question by telling you what the problem is: When computers were being built in the 50's and 60's no one gave much thought to the new millenium, as evidenced by everyday forms that have 19 before the final 2 digits of the year. My checks drawable on US banks all have that 19. How does this affect us and what will shut down? Early IBM PCs and compatibles have a bios chip that is not capable of identifying the year as 2000, since most of these were not capable of going past the late 80's, it is doubtful that they are in use (at least not without a bios revision). These are pre-286 models. So called "Big Iron," mainframes and minicomputers will not have this problem. Much of the software assumes it is 19xx-something. What this does is makes it impossible for safely computing interest rates and registering things like births and deaths in 2000+. Even some of the "fixed" software has trouble. I have an electronic form that I purchased, it accepts 1999, and 2001, but not 2000. I am after the company that built the form to send me a fix. Anyway, computers will not automatically stop working Jan 1, 2000. Hospitals will not stop working, equipment will not fail, banks will not blow up, and your credit card company will not forget how much you owe them (damn the bad luck!). What will happen is any computation that requires a pre-2000 date will not be reliable if the date has been recorded in a DD-MM-YY format. For example, if the computer's software reads 2000 as year 00 and my 1955 birth date as 55, then the computer would compute my age as -55 years old (I can only wish ;-) ). Only those programs using a DD-MM-YYYY format will be reliable. This is why Y2K companies go into firms, analyze their software, and update it as necessary to provide for the complete year. This is in truth an impossible task because of the nature of computer programs and computer programmers (bad code, no documentation). Jan 1, 2000 may actually be a field-day for the average Joe. Lawyers are lined up in anticipation of all of the lawsuits, class action and other wise, that will be filed against banks and the government. Anyway, affect on hospitals and Xoma is zip, other than they may not be able to immediately bill you for services or verify your insurance is current. Can't imagine with the problem being identified that they are going to risk denying services, just in case it is a computer glitch. Something to consider is that this problem will identify itself before Jan 1, 2000. Any organization that works on fiscal years will identify it at the beginning of the fiscal year. For example, the US Federal government's fiscal year 2000 starts Oct 1, 1999.