Step 5 - Correct Year 2000 Problems

WARNING: DO NOT ATTEMPT TO TEST OR CORRECT ANY Y2K PROBLEMS WITHOUT HAVING FIRST COMPLETELY BACKED UP ALL PROGRAMS, FILES, APPLICATIONS OR RECORDS TO AN EXTERNAL DEVICE.  Backing up your data to a segregated area on the computer may not protect you from Y2K  failures.

The specific measures required will vary from department to department, depending on the problems identified in the assessment steps above. Some general guidelines: Determine who will make necessary changes - someone within the ITS, your unit, other person with specific technical expertise. Set realistic time lines and mileposts within your overall year 2000 project plan for each application or process to be updated or converted.

Schedule fixes and implementation/testing schedules based on the criticality of specific processes and applications. Date-sensitive processes and applications essential to the research, academic or administrative functions of the department must be addressed first.

Hardware

Let ITS know via the Inventory what you have. If the department coordinator has not been contacted by ITS before July 1, 1999, you must contact the ITS Y2K Liaison for assistance.

Software

Contact ITS for advice or assistance.

Applications

Contact ITS for advice or assistance.

Interfaces between applications or programs, as well as transferred data or shared databases, constitute an area of high risk for year 2000 failure. Where such interfaces exist, it is essential that year 2000 planning, solutions, and testing be closely coordinated among College departments and external agencies.

Manuals and documentation

Be sure to update all user manuals, help files, and documentation to reflect any changes, especially if the change means differences in the way dates are entered into the application, or if interfaces to other applications are modified.

Back to Tool Kit Steps

Go to next step

Return Home