Also found in: Dictionary, Thesaurus, Acronyms, Wikipedia.


This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)
The following article is from Conspiracies and Secret Societies. It is a summary of a conspiracy theory, not a statement of fact.


As the calendar moved inexorably toward the year 2000, a new millennium, apocalyptic fever seized millions.

Millennium means a period of one thousand years, but the Millennium signifies the return of Jesus and the end of the world as it presently exists. There seemed a strange kind of foreboding among a sizable portion of the populace that at the end of the current millennium (1000–2000), humankind was going to pay for its sins. The world was coming to an end. Judgment Day was upon the whole of humanity. And whether one feared a wrathful God or a depleted planet didn’t matter. Either way, when the sun arose on January 1, 2000 (if, indeed, it rose at all), it would shine on whatever rubble remained of an old world destroyed or a new world being born. There was hope only for a righteous few who would welcome the Rapture lifting them up to the skies, Jesus returning to conquer evil, or perhaps scientific salvation that would allow some of Homo sapiens to survive.

And finally, there were those who shrugged and said, “What’s the big deal? January 1, 2000, is just another day.”

Frightening rumors kept vast audiences up all night listening to radio talk shows. There was this incredible thing about computers. They weren’t programmed to work beyond December 31, 1999. At the stroke of midnight, lights would go out all over the world; power plants would shut down; electrical appliances—from furnaces to toasters—would be useless. One of the most frightening Y2K (meaning “year 2000”) visions was that passenger and military aircraft all over the world would fall from the sky because their computers would shut down.

Thousands of stalwart individuals, determined that they and their families would survive Y2K, bought wood-burning stoves, kerosene lanterns, generators, and firearms. Millions of homes stocked up on canned goods, bottled water, and batteries.

Tabloid newspapers joined the radio and television talk shows in bombarding an already nervous population with prophecies of the coming apocalypse as elucidated by historians, scientists, theologians, Bible scholars, futurists, aboriginal seers from many cultures, psychic-sensitives from around the world, and UFO contactees channeling advice from outerspace intelligences. A 1997 Associated Press poll revealed that nearly 25 percent of adult Christians believed that Jesus would return on January 1, 2000, or soon thereafter to set in motion the terrible events prophesied in the books of Daniel, Ezekiel, and Revelation.

As the year 1999 progressed, Israel deported members of Concerned Christians, a cult that had come to Jerusalem to plan the battle of Armageddon that would launch the Second Coming of Christ. The founder of the group, Monte Kim Miller, believed that he was the final prophet on Earth before Jesus’s return. Miller had been told by God that he would be killed in Jerusalem’s streets in December 1999 but would rise from the dead in three days.

A former kibbutz worker named Jacob Hawkins changed his name to Yisrael and prophesied that the world would end if the laws of Yahweh were not universally followed. Yisrael soon had nearly three thousand followers who believed that he would announce the exact time of Jesus’s return—if Satan didn’t murder him first.

Sergei Torop was dismissed his position as sergeant with a Russian police unit when he began to have religious visions. Torop changed his name to Vissarion, revealed that he was Jesus returned and, with thousands of followers, began building a “City of the Sun” on Siberia’s Mount Sukhaya.

Fifty miles from Little Rock, Arkansas, a former Mennonite minister, Robert Millar, built Elohim City, a paramilitary fortress, in anticipation of the endtimes. Millar believed that a series of cataclysms would strike the United States soon after the year 2000 and cleanse the unworthy and wicked from the Earth.

As millions were stockpiling firewood, bottled water, canned goods, and other necessities to withstand the apocalypse, some worriers posed the question of whether the millennium would actually begin on January 1, 2000—or January 1, 2001.

Stephen Jay Gould, professor of zoology and geology at Harvard and an author of books about science, history, and philosophy, released his Questioning the Millennium: A Rationalist’s Guide to a Precisely Arbitrary Countdown in 1997. Gould discusses the human “fascination with numerical regularity” and notes that some philosophers have divided earthly history into a cycle of four based on the Four Empires in the apocalyptic chapters of the book of Daniel; others have advocated a fivefold division based on the five sequential political societies mentioned by Plato. “The millennium has been predicted and expected at almost any time, depending on the system in favor,” Gould writes. “Obviously, with Thomas Muentzer advocating 1525, William Miller 1844, Wovoka 1890, Chilembwe 1915, the year 1000 or 2000, and intervals of 1000 in general, could claim no special preference.”

When January 1, 2000, came without the world ending, and so did January 1, 2001, most of the world breathed a sigh of relief and smugly observed that the eternal clock is still ticking. Others pointed out that in the eternal scheme of things, what’s a five- or six-year delay when you’re dealing with a thousand or more?

Conspiracies and Secret Societies, Second Edition © 2013 Visible Ink Press®. All rights reserved.

Y2K compliant

Capable of correctly processing any data that deals with a date beyond the year 1999. See Y2K problem.

Y2K problem

(Year 2000 problem) The inability of older hardware and software to recognize the date after the year 2000. The reason they could not was because the year was stored with only two digits in many databases; for example, 12-11-03 instead of 12-11-1903. Therefore, after the turn of the century, was this date 1903 or 2003? Every program that dealt with dates could have problems.

Dates Are Critical
Financial transactions often match dates in database records with today's date or with a future date. If the system does not handle dates correctly, bills do not get paid, notices do not get triggered and actions are not taken. After 2000, any system that could not recognize the change would cause erroneous output with applications that dealt with future dates. Although warnings of disaster prevailed, there were only a few incidents when all was said and done.

Fixing It Was a Massive Job
The solution to this "millennium bug" required upgrading hardware to support four-digit years, converting files and databases to four-digit years and converting all the software that referenced dates. Enterprises had a huge amount of legacy data files and thousands of programs that accessed them. With many older applications, the programmers who wrote them were long gone, and documentation was lacking. In many instances, the source code was missing. Even when changes could be made, the time it took to test them was taxing on the IT staff.

Just to Save Two Bytes!

The problem originated with punch cards that go back to the early 1900s. In order to cram an entire order or customer record into a single punch card with 80 or 90 character columns, the year was shortened to two digits. Why waste two columns for "19" when it was going to be "19" for a very long time. When punch card systems were converted to magnetic tape in the 1960s, and there was ample room to convert to four digits, laziness prevailed because 2000 still seemed very distant. Saving two columns (two bytes) in a punch card was appropriate, but not when there was ample storage on tape.

Problems Occurred Even Before 2000
For example, imagine a company wanting to delete customers who had not purchased anything in the previous five years. The program logic would add 5 to the year of the last order and compare the result with the current year. Suppose a customer last ordered in 1995 and the current year were 1996. Add 5 to 95 in a non-Y2K compliant system and the result was 00, not 2000. Since 96 was greater than 00, the customer record would be deleted. See data aging and Year 2038 problem.

The Y2K Problem
When data were copied from punch cards to magnetic tape records starting in the 1960s, the two-digit year was generally copied verbatim because the next century seemed very distant. See 3 C's.

About Time
This conference was from the Software Productivity Group, an organization that provided the necessary training to deal with this sticky subject. (Image courtesy of Software Productivity Group)

Making a Strong Point
Year 2000 compliance software from Isogon was used to test IBM mainframe applications running the MVS operating system. (Image courtesy of Isogon Corporation.)

Perhaps Overly Dramatic
There was a lot of concern before the millennium that things could get out of hand. However, had the world not spent hundreds of billions of dollars revamping thousands of applications, there would have been many problems. There were only a few.

Even Before Y2K
Program maintenance is always a problem in this industry. This commentary from PROCASE Corporation was created more than a decade before Y2K. PROCASE provided software that could flow chart a program from its source code in order to make it understandable.
Copyright © 1981-2019 by The Computer Language Company Inc. All Rights reserved. THIS DEFINITION IS FOR PERSONAL USE ONLY. All other reproduction is strictly prohibited without permission from the publisher.
References in periodicals archive ?
Or perhaps we should put out a rumor that because of a programming glitch in UNIX, Y2K won't arrive until 2005, but that it will definitely come.
The ultimate threat to a mainframe computer staff was that Y2K would oblige them to write themselves out of a job.
The thrust behind the newsletter was to provide practical guidance on legislation, litigation, liability; arbitration, SEC disclosure guidelines, FCC administrative regulations and policies, and equipment manufacturers who had Y2K compliant products.
In hindsight, it may be easy to snigger at doomsayers who genuinely were afraid of the so-called Y2K bug, but experts say their concerns may have been justified.
* established a Y2K speakers bureau whose members participated in meetings throughout the county,
Problems brought about by Y2K, Dobson asserted, could also lead "present political leaders" to "refuse to yield power," and he added that the computer bug could even spark "God's judgment -- and that one, obviously, overrides all the rest of them."
According to another e-legend, if the Y2K bug didn't shut civilization down, the Feb2K bug will.
Nonetheless, Gannett was still the third-highest Y2K spender among the 13 publicly traded newspaper companies that made data available.
IDC's Project Magellan, a research effort that has studied Y2K preparations worldwide and that also monitored the beginning of the new year, estimates that Y2K-related computer downtime will take USD21bn out of the global economy in 2000.
The Singapore government, confident that the city state will be able to avoid major disruptions due to the Y2K bug, Thursday urged people to party on New Year's Eve instead of worrying about the Y2K bug.
1 Kyodo Thailand passed Saturday through the turn into 2000 without any Y2K bug problems in its national computerized systems.
As you read this, the famous (or infamous) Y2K problem will be assumed by many to have come and gone.