The best Y2K testing - setting the clock ahead (on a test server), aging database information, and then processing a comprehensive set of transactions and doing all batch processing for all cycle - will identify most Y2K problems. But there is never a guarantee that all Y2K problems will be found. Writing and fixing software is an art, not a science. So departments should expect some (even if few) problems with customized applications they are responsible for.

Y2K problems in online and batch systems are most likely to appear on the first day of online processing in January, and when each batch process is run for the first time in January. Thus there can be significant benefits to having all IS staff at work or on call during the entire first two weeks in January, including the first two weekends in January. Such a staffing decision must be made by departmental management.

Similarly, Y2K problems with servers and desktop and notebook computers are likely to appear in the first two weeks in January. So having all IS staff at work, or available, during the first two weeks in January seems to be the most prudent course of action. Again, such a staffing decision must be made by departmental management.

It seems much less critical to have IS staff at work or on call for the period January 15-28th, assuming that any Y2K problems that appear by January 10th can be dealt with by mid-January. But the last few days in January and/or the first few days in February, if there is any month-end processes being run, can also be a critical period where staff availability is important.

Department managers that are not familiar with procedures for having employees be available for work on non-scheduled days, or to actually work on should contact the campus Human Resources department for guidance.

Return to the main Rollover Planning page