| 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. |
| Y2K ready | This expression has been used with several different, and contradictory, meanings: 1. Y2K compliant. 2. Ready for Y2K, but not necessarily Y2K compliant; implies the organization has contingency plans in case computer systems fail. 3. Able to handle date manipulation and store four-digit dates, but not requiring the user to enter a four-digit year. |
| Y2K readiness plan | A detailed plan for bringing an organization’s system into Y2K compliance. |
| YY | A two-digit-year date format; for example, 95 for 1995. |
| YYYY | A four-digit-year date format; for example, 1995 for 1995. |
| Year 2000 remediation | The process of revising a system to make it Year 2000 compliant. |
| Year 2000 readiness plan | A detailed plan by which an organization will bring its computer systems into Year 2000 compliance. The phases of such a plan must include planning, assessment, remediation, testing, further corrections as necessary, and testing again until the system is fully Y2K compliant. |
| Y2K Challenge | The challenge to an institution to respond to the Y2K problem. |
| PMP | Project Management Plan. A detailed description of an organization’s strategies for resolving Y2K issues. |
| Project Management Plan | (PMP). A detailed description of an organization’s strategies for resolving Y2K issues. |
| two-digit-year format | A format in which a year (such as 1995) is represented as two digits (95), only practical if all dates are within the same century; for example, this format cannot distinguish between 1995 and 2095. |
| remediation contingency plan | A plan which will go into effect if an institution’s Year 2000 readiness plan is not completed in time. |
| production environment | The system environment in which an organization’s data processing is accomplished. |
| point-to-point test | A test of the ability of a system to transmit data directly to another system. |
| parallel test | A comparison of the results of a process run concurrently in the old and new systems. |
| sliding window | A technique for determining the century (high-order digits) of a year that is represented in two-digit format, which is a variation on the fixed window remediation technique. In this method, the pivot point changes when the system year (usually the current year) changes. A 100-year window is designated, spanning two centuries. For example, if the pivot year is 70 during 1998, then during 1999 it will be 71. If the window is set at 35 future years (1971-2005) and 64 past years (1906-1969), dates in the range 00 through 05 will have the century field 20 because they fall into the future window. Dates in the range 06 through 99 fall into the past window and will have the century field 19. |
| Year 2000 transition | The revision of a system and its programs so it can correctly process dates outside the range of 1900-1999. |