Just when you thought the century date change was behind you, it's time to prepare for another critical date: Feb. 29, 2000. Just like the lack of foresight that resulted in the "Y2K Bug," it seems that computer programmers may also not have considered that the Year 2000 would be a leap year, lasting 366 days, rather than 365.
There are two rules governing the determination
of leap years:
1. A year evenly divisible by four is a leap year, except for years ending in 00.
2. A year ending in 00
is a leap year only if it is
divisible by 400.
Thus, 1900 was not a leap year, but 2000 is.
The potential for the leap year error is greatest in embedded systems, such
as those found in card readers or stoplights.
But the problem may also exist in software applications. The good news is that the public is generally unaware of the potential for problems, and therefore, the Fed does not expect to experience increases in cash demand.
Financial institutions have had opportunities to test with the Fed for the 2000 leap year date since June 1998, and many District institutions have already tested with us. If you have not tested, however, or would like
to retest, a majority of Fed applications will be available for testing on
the following dates:
Jan. 20/Feb. 15
Testing for Feb. 28, 2000
Jan. 21/Feb. 16
Testing for Feb. 29, 2000
Jan. 22/Feb. 17
Testing for March 1, 2000
Other dates are available for some applications.
Details on which applications can be tested on any of these dates are
in the test schedule sent to you in mid-November. To
register, contact Electronic Access Support at 1-800-333-0861.