by Liz Taylor
The "Year 2000" date problem (or the "Y2K" problem as it is also called) which appears to be everyone's latest obsession, occurs when computer software has been programmed to read a year as two digits and makes the assumption that "01," for example, actually means "1901." This seemingly insignificant but fairly common practice is poised to wreak havoc as the new millennium approaches and computers everywhere are unable to distinguish this century from the next one. If the problem isn't rectified soon-and globally-we could witness world-wide pandemonium as computers blithely calculate erroneous results for any computation involving a year later than 1999. On January 1, 2000, systems (and the organizations that depend upon them) could come crashing down all over.
CUNY has been working on the Y2K problem for some time and many of its systems are already "Year 2000-compliant." However, you should also be aware that to address the Y2K problem fully, each department must also have an action plan in place to ensure the compliance of all departmental hardware, software, systems, and equipment.
Vice Chancellor Richard Rothbard has set up a Y2K Task Force and FYeI is doing its part by devoting this entire issue to the steps CUNY has already taken or will soon take regarding the problem. In addition, we will delineate many of the concerns, as well as a number of helpful resources to help departments handle the Y2K issue in a responsible and comprehensive manner. We hope this information is useful.
CUNY's Year 2000 Efforts
CUNY has been taking a systematic approach to the problem by:
2. continuing to raise awareness about the problem through intra-university communications, such as FYeI;
3. defining compliance and methods used to achieve it, as well as software, equipment, or procedures which may be affected by non-compliance (see page 8);
4. developing a CUNY Year 2000 Web site which will feature regular updates on Y2K concerns. (See future issues of FYeI for more information about the Web site);
5. discussing legal issues and providing state recommended contract language for purchasing agents within the University (see pages 12-13);
6. identifying other helpful Web resources, such as commonly used software and hardware vendor sites and other general Y2K information sites (see pages 15-16); and
7. establishing a CUNYVM and CUNYJES3 Year 2000 test environment where departments can test their programs for Y2K compliance.
Got a Y2K suggestion?
If you are aware of any information or resources that might benefit CUNY departments, please tell us about them. You can reach us at:
FYeI
555 West 57th Street
16th Floor
New York, NY 10019
(212) 541-0317 (phone)
(212) 541-0357 (fax)
lizbh@cunyvm.cuny.edu