Make your own free website on Tripod.com
Recommended Resources
Cyberhaven.com Offshore havens, asset protection, global investing and other useful techniques.
The Year 2000 Bookshelf Books to help your evaluate the Y2K problems you face.

Gary North's Y2K Links and Forums - Mirror

Category: Imported_Data

(feel free to mail this page)



(Links to documents appear after the summary.)

This, in my view, is the biggest unsolvable problem of the y2k challenge. If a company somehow revises its computer systems' legacy code, tests it by parallel testing, does not crash its systems during the testing, and transports all of its old data to the newly compliant system, it faces a problem: it is part of a larger system. Computers transfer data to other computers. If the compliant computer imports data from a noncompliant computer, the noncompliant data will corrupt the compliant system's data. A company may have spent tens of millions on its repair, but once it imports noncompliant data, it has the y2k problem again.

Next, if a compliant computer sends compliant data in a compliant format to another computer, this transfer may crash that computer. Or the recipent computer may not recognize the compliant format. The system breaks down.

A noncompliant compuer's data can corrupt a compliant computer's data. But those in charge of the compliant computer may not recognize this when it happens. They may then allow their supposedly compliant computer to spread the data with others. Like a virus, the bad data will reinfect the system. I describe this dilemma as "reinfection vs. quarantine."

Every organization that operates in an environment of other organizations' computers is part of a larger system. If it imports bad data from other computers in the overall network, the y2k problem reappears. But if it locks out all data from noncompliant sources, it must remove itself from the overall system until that system is compliant. This threatens the survival of the entire system. Only if most of the participants in a system are compliant will the system survive.

Consider banking. A bank that is taken out of the banking system for a month -- possibly a week -- will go bankrupt. But if it imports noncompliant data, it will go bankrupt. A banking system filled with banks that lock out each other is no longer a system.

There is no universally agreed-upon y2k compliance standard. There is also no sovereign authority possessing negative sanctions that can impose such a standard. Who can oversee the repairs, so that all of the participants in an interdependent system adopt a technical solution that is coherent with others in the system?

Corrupt data vs. no system: here is a major dilemma. Anyone who says that y2k is a solvable problem ought to be able to present a technically workable solution to this dilemma, as well as a politically acceptable way to persuade every organization on earth to adopt it and apply it in the time remaining, including all those that have started their repairs using conflicting standards and approaches.

Some people say that y2k is primarily a technical problem. Others say it is a primarily managerial problem. They are both wrong. It is primarily a systemic problem. To fix one component of a system is insufficient. Some agency in authority (none exists) must fix most of them. Those organizations whose computer systems are repaired must then avoid bankruptcy when those organizations whose systems are not compliant get locked out of the compliant system and go bankrupt.

If there is a solution to this dilemma, especially in banking, I do not see it.

Updated - Subject

13-Jan-97   No Date Standard = Chaos in Year 2000
24-Feb-97   Corrupt Data: How to Ruin a Compliant Computer
25-Mar-97   There Is No Agreed-Upon Standard
19-Sep-97   The Navy Describes the Interconnection Problem
23-Sep-97   British Police Describe the Coordinated Repair Problem
02-Oct-97   Shared Data: The Nuclear Regulatory Commission's Warning
22-Oct-97   Suppliers and Buyers Must Adopt Coherent Y2K Solutions
25-Oct-97   Six Largest Canadian Banks Coordinate Y2K Repair
30-Oct-97   Destruction or Breakdown of Government Files
03-Nov-97   Defending Against Noncompliant Data
04-Nov-97   Health Care Industry: Bad Data Problem
08-Nov-97   Spreadsheets from Micros Can Corrupt Compliant Mainframes (if Any)
02-Dec-97   It's a Problem for Society, Senior IT Officer Says
20-Jan-98   No Standards for U.S. Government Until March 1, 1998
24-Feb-98   Toxic Data, Says Lawyer
16-Apr-98   Bad Data from Accounting Firms
20-Apr-98   New Zealand Government Report's Warning
22-Apr-98   Ignored Problem, Expert Says
22-Apr-98   More Interconnections Means Vastly More Vulnerability
29-Apr-98   Why Y2K Is a Systemic Problem: Fusion into One System
05-May-98   Thailand's Y2K Budget Blocked by Budget Bureaucrats
27-May-98   Y2K as Ebola: The Re-infection Problem


Return to Main Categories

Return to Home Page