My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Agenda Packets - 1999/02/01
MoundsView
>
Commissions
>
City Council
>
Agenda Packets
>
1990-1999
>
1999
>
Agenda Packets - 1999/02/01
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/28/2025 4:46:12 PM
Creation date
6/14/2018 6:01:45 AM
Metadata
Fields
Template:
MV Commission Documents
Commission Name
City Council
Commission Doc Type
Agenda Packets
MEETINGDATE
2/1/1999
Supplemental fields
City Council Document Type
City Council Packets
Date
2/1/1999
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
113
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
uw:izs -./...t:_5..—_y/._.L- / t��T /_ t' " FT'I;J <br /> YEAR 2000 PROBLEM <br /> Call it the Year 2000 problem or the Y2K problem and it sounds like a technical problem;call it the Millennium Bug <br /> and it sounds like an end-of-the-world science fiction thriller. Whatever the name,however,the problem is real. <br /> Nobody is sure what computers--or for that matter,any of the countless devices and systems controlled by <br /> microchips--are going to do at the stroke of midnight when December 31, 1999 rolls over to January 1,2000. <br /> Some computers and systems will make the change smoothly;while others may behave erratically or even <br /> stop working. <br /> Why? During the early days of computing,when processing power and storage capacity were puny com- <br /> pared to what we're accustomed to today,programmers and engineers decided to reduce the space needed <br /> to store a date by recording only the last two digits of the year: Valentine's Day 1980,for example,was stored <br /> as 021480(they also saw no reason to store the slashes between the month,day,and year). When this century <br /> ends and the new one begins,however,that will become a problem. Computers won't know the difference <br /> between Valentine's day, 1901,and Valentine's Day,2001;they will both be stored as 021401. <br /> Traditional mainframe computers,which are dominated by older programming languages--COBOL,FORTRAN, <br /> and others--will certainly be affected. These programming languages are where the problem has its roots. <br /> But virtually anything and everything that relies on embedded process controllers(microchips) <br /> will be affected. The first thing that comes to mind is the personal computer. Many older IBM <br /> compatible PCs won't be compliant,but machines sold after 1997 generally are compliant. <br /> Macintosh computers don't have a Year 2000 problem,because they store the date as a long ..'_ <br /> number based on the number of seconds since January 1,1904. This system handles the 2000 <br /> just fine,but apparently has its own problem at 6:28:16 a.m.,February 6,2040 when the total num- <br /> ber of seconds since January 1,1904 will be too long a number for the allotted storage space. <br /> Microchips also control security elevators and doors,telephone switches,traffic lights, and electric utility <br /> substations,as well as small household and office appliances. Industry experts predict that of the 25 billion <br /> chips in electronic components,only about 2 percent will fail, because most of these devices lose track of <br /> their timing functions. But there's no way to know which 2 percent. In many(perhaps most) cases,the <br /> device will just stop working. Elevators will descend to the basement or go into security mode;VCRs will <br /> work but you won't be able to program them. <br /> The problem is not just one of hardware and chips. Any software that stores and uses dates--spreadsheets, <br /> databases,financial management software of all kinds,human resources software,and a host of other programs-- <br /> is vulnerable to the Year 2000 problem. By extension,so are all the data files used by those programs. <br /> In short,anything electronic that depends on dates or on calculations involving dates is vulnerable. Y2K <br /> -1- ®M„D <br />
The URL can be used to link to this page
Your browser does not support the video tag.