Knowra Year 2000 problem Year 2000 problem The Year 2000 problem was a software and hardware bug caused by storing years with two digits, which could make dates around 2000 be misread or miscalculated.
Date representation : Methods for encoding calendar dates in data, including numeric fields, text, and timestamps. The problem began when systems encoded years without enough information to distinguish centuries.
Y2K compliance : The condition of a system being tested and corrected to handle dates around and after 2000. Organizations used compliance programs to identify and repair date-related defects.
Memory economics : The tradeoffs between data storage capacity, cost, and the benefits of keeping information compact. Limited and expensive storage made saving two year digits seem worthwhile.
Y2K scare : Public concern that computer failures at the turn of 2000 could disrupt essential services and everyday life. Warnings and uncertainty made the technical risk a prominent public fear.
Two-digit year : A year representation that stores only the final two digits of a year. This compact format made 1900s and 2000s dates ambiguous.
Y2K remediation : The process of modifying, replacing, or testing systems to address Year 2000 defects. Remediation included code changes, hardware replacement, and contingency planning.
Legacy system : An older computer system that remains in use because it supports ongoing operations or data. Long-lived systems preserved date assumptions long after their original design.
Y2K bug predictions : Forecasts of disruptions from Year 2000 defects, ranging from localized failures to widespread infrastructure breakdowns. Comparing predictions with outcomes helps explain later disputes over the threat's scale.
Pivot year : A cutoff used to interpret two-digit years as belonging to one of two centuries. Systems used cutoffs to guess which century an abbreviated year meant.
Mainframe computer : A large computer designed for high-volume transaction processing and centralized data management. Many legacy business applications ran on mainframes with date fields requiring review.
Show all 21