Tested and proven capable of correct identification, manipulation, and calculation using dates outside the range of 1900-1999; or not dependent on dates in order to function.
YMARK2000
A testing tool for Year 2000 compliance from NSTL.
Y2K OK
Ready for the Year 2000.
Y2K baseline inventory
An initial inventory of system data using 54 of 108 data elements identified by the Air Force Year 2000 Working Group.
Y2K event horizon
The year a system is expected to experience Year 2000-related problems
as a result of date projections.
Y2K compliant
Tested and proven capable of correct identification, manipulation, and calculation using dates outside the range of 1900-1999; or not dependent on dates in order to function.
Y2K noncompliant
Tested and proven not capable of reliably using dates outside the range of 1900-1999.
Y2P
Year 2000 Problem. In the 1980s and before, most computer programs were designed to store only the last two digits of the years on all dates. When the Year 2000 comes, these programs will show dates of 00, which may be interpreted the same as 1900. This discrepancy may cause widespread problems, especially in the large computer systems used in government and big industries. Efforts to correct the problem before 2000 may be too late.
Year 2000 noncompliant
Tested and proven not capable of reliably using dates outside the range of 1900-1999.
Year 2000 Problem
(Y2P). In the 1980s and before, most computer programs were designed to store only the last two digits of the years on all dates. When the Year 2000 comes, these programs will show dates of 00, which may be interpreted the same as 1900. This discrepancy may cause widespread problems, especially in the large computer systems used in government and big industries. Efforts to correct the problem before 2000 may be too late.
