Attachment to UIPL No. 38-98
Date Specific Y2K System Compliance
Background
Validating Y2K compliance requires demonstration that all date sensitive requirements have been satisfied. Attached are lists of various dates, intervals, and days of the year that should be used to help validate SESAs' systems for Year 2000 compliancy. The lists have been compiled from industry best practices sources.
Discussion
To achieve minimum compliance, it is strongly suggested that all application software and associated operating systems be able to accurately process the Y2K date sensitive requirements. The requirements have been separated into four lists to highlight the particular Y2K sensitivity.
Special Dates to Test for Y2K Compliance
LIST I
Special Dates
DATE COMMENT 01/01/1999 Testing for Non-Standard uses of 99 as a flag 09/09/1999 More flag testing 12/31/1999 Last day of 1999 01/01/2000 First day of year 2000- should be a Saturday, 01/01/1900 was a Monday 02/29/2000 Tuesday, not a valid 199x date 03/01/2000 Wednesday, 03/01/1999 is Monday, 03/01/1900 was a Thursday 10/10/2000 First double digit date, double month date 12/31/2000 End of 2000 01/01/2001 Start of new millennium
LIST II
Date Intervals
This list identifies suggested from/to date combinations for which correct and successful "time rollover" needs to occur. For the "from" time it is suggested to be 23:55:00; the "to" time should be 00:05:00.
FROM DATE TO DATE DATE INTERVAL 2/31/1999 01/01/2000 10 minutes 02/28/2000 02/29/2000 10 minutes 02/28/2000 03/01/2000 1450 minutes
(24 hours + 10 minutes)02/29/2000 03/01/2000 10 minutes 2/31/2000 01/01/2001 10 minutes
LIST III
Days of the Year
If the system processes and produces 'day of the year' values then it is necessary to ensure that the correct day of the year for all days in 2000 and beyond 02/28/2000 are correct. Examples include:
Day-of-year (02/29/2000) = 60
Day-of-year (03/01/2000) = 61
Day-of-year (12/31/2000) = 366
LIST IV
Miscellaneous Dates
Develop an offset value to insure that the date/day coordination is handled properly (e.g., adding 28 years to 1996 dates ensures that 2024 dates fall on the same day).
Verify that all date offset formulas are synchronized with unique industry requirements (e.g., cannot have a bank posting date on Sunday).
Special firsts or lasts or system critical dates (i.e. Fiscal years, etc.) should be tested, such as first Pay Period, first Billing Period, First/ Last day of Accounting
Period, first end of month, first end of quarter, etc., to assure that system will function successfully past 1/1/2000.