ArchiveSCV
the-signal.com. The Santa Clarita Valley Signal. Back to the collection.

· the-signal.com, Wayback capture

LOREN CASSELL / Y2K Consultant

Y2K: Is it the end of the world?

One year from today we might be reading by the light through the window about the collapse of our social infrastructure, wishing we had some hot coffee instead of the lukewarm eggnog from the refrigerator.

On the other hand, we could be in our warm homes, somewhat disappointed not to see fire-and-brimstone stories but quite thankful that all of the doom-sayers have gone back to wherever they hide.

Will we be trying to avoid that miserable "I told you so" neighbor on our way to work? Will we even have a place to work? Instead of a brown bag lunch will we carry those military-green MREs? Will we have to start farming corn in our driveways and grind wheat like the Amish?

These scenarios seem as unlikely as the chance that you'll eat the mail-order fruit cake you got for Christmas. But these are the predictions being made by mature, knowledgeable experts following the Century Date Changeover, or CDC.

Y2K. The "Y" is for "year," the "K" is for "thousand" — that's "Year 2000," as in January 1, 2000. Just about 280 business days from now, computers all over the world will interpret the year 2000 date code as 1900.

Early programmers and system designers abbreviated the code for the year from four digits to two, saving lots of expensive memory and disk space. This practice was so commonly accepted that it might not have been a conscious decision. Maybe they thought systems or software would be easy to fix when the day arrived. Maybe they were thinking the systems or software wouldn't be around in the year 2000, or that they wouldn't be around in the year 2000 to answer for them.

Whatever their rationale, the results will be miscalculations, crashing systems, freezes and corrupt data problems in three types of computers: mainframes, personal computers (including the Mac), and embedded controllers (which average about ten for every person on earth).

The problem is in hardware, software and firmware. An estimated 350 million to 800 million lines of programming code need to be fixed. To understand scope of it, figure that there are 60 lines per page and 500 sheets in a two-inch ream of paper. At 350 million to 800 million lines, you could see the top of the stack from the window of the space shuttle. There is no way on earth — no pun intended — to get that much work done by Jan. 1, 2000.

They've coined lots of clever names for the scenarios that may afflict us. It seems the proverbial pendulum has been swinging from dark denial on one side to enlightened insanity on the other.

Two years ago if you had asked me or any other IT professional how bad the problem was, you probably would have gotten a smug, "No big deal" response. But the scope of the problem has dawned on us since then. Now ask the same person about triage, pivoting, or data windowing. The blank stare tells you haven't been in the trenches lately.

We do know what's going to happen to mainframes and PCs. We can analyze the hardware and the software. The embedded controllers are harder to figure out because the hardware is tucked away in some oil rig or satellite, and God only knows where the "firmware" documentation is.

The doomsday scenarios result from the two complex questions we can't answer: How will all these systems interact with each other in a modern, interconnected society? And what is the real status of the rest of the world?

We can see what is possible, but we can't calculate what is probable. So the Hollywood screenplays fall within the scope of possibility.

When will the problems occur? Although many are describing Y2K as the "bomb," it now looks more like a fire. The problems have already begun, and they will continue before, during and after the CDC.

Most of the embedded controllers will fail on 1-1-00. That's when they will see the first bad date. The mainframes and the PCs could encounter invalid data from any number of data inputs (including keyboards). They will fail when they use the bad date codes to calculate, compare, reference or sequence a date or a list of dates.

Examples are an airline reservation date input 333 days before Jan. 1, 2000, or a driver's license expiration date that extends into the new century.

The biomedical department at the Pitt County (NC) Memorial Hospital decided to test a ventilator. They set up the equipment to do a "rollover" test — they set the date and time just prior to the CDC and let it count down. When the clock flipped over, the ventilator failed.

They contacted the manufacturer, who instructed the technicians to remove a cover and flip an internal switch. After resetting the power to the machine, it operated correctly.

Rick Smith, IS auditor for the hospital, asked, "How could we have known about the hidden switch? And how many other biomedical vendors haven't even heard of Year 2000 yet? Frightening indeed."

Moviegoers paying with credit cards discovered earlier this year that they could not purchase box office tickets at nearly 100 AMC theaters if their credit cards expired in 2000 or later.

In an April 27 story, Fortune magazine quoted General Motors' worldwide spokesman as saying there are "catastrophic problems" in every GM plant. Peter de Jager, one of the earliest authors and speakers on Y2K issues, elaborated: "(General Motors) took a plant which they were going to shut down, and instead of shutting it down they rolled the clock forward. ... Their assembly line — the robotics — stopped. They just stopped."

Food distribution lines, railroad scheduling and switching, phone pagers, satellites, medical equipment, water treatment plants, electrical switching stations, aircraft, air traffic control systems, traffic lights, ATMs, banks, sewage treatment plants, hospitals, 911 systems are affected — to name just a few.

The best advice I can give you as an IT professional is to aggressively push through the 5-step process outlined in virtually all business preparation documents: Awareness, Inventory, Remediation, Test, Implementation.

The best advice I can give you as friend and neighbor is to tuck that fruitcake away in the garage and pray that God will pick us up out of this miserable mud hole, show us mercy, and clean us up.

The following Internet sites contain important information for business and personal preparations: www.cassandraproject.com , www.josephproject.org , www.year2000.com , www.senate.gov/~bennett , www.yardeni.com , y2knews.com .

* * *

Loren Cassell, a Y2K consultant, is the manager of information systems for a Valencia aerospace firm. "Inside Business" appears Sundays and rotates among SCV business leaders.

← Back to 1998

About this record

How it was held, read and classified

Record details

Morris ID
Not a Morris ID. This record is keyed ts-df:/business/guest/122798.html.
System
other
Reading copy
the-signal.com
Chosen by: only copy held. On this copy: words 1,109 (e-mail addresses counted as one token); reader comments 0 (counted, not reproduced here); images 0.
Extracted by
datefile:SLUG_to_rule
signal-extract/0.15 (2026-11-16)

Other copies

Held
None. The holding has this article from one host only.

How it was classified

Label
clearly-local
Judgment
A machine’s (recorded as machine), kept as one so it can be revisited.
Classifier
signal-localclass/0.7 (2026-11-12)
Local signals
  • text:valley_names [2 distinct/2 mentions: SCV, Valencia]
  • byline:named_writer_no_wire_credit [Inside Business With]
National signals
none fired
Scores
local 4, national 0