As you might expect, given that we're the Academic Computing and Communications
Center, we have lots of stuff that might have problems with the year 2000.
Fortunately, much of what we use now are commercial products, so we hope
to be able to solve most of our own year 2000 problems with vendor-supplied
upgrades. (These days we're making a specific effort to use non-modified
commercial products as much as we can. We learned the hard way that this
is a good thing: by having invented several wheels that we've had to re-reinvent
time after time, as we upgrade, replace, or add new systems.) But we also
have a lot of homegrown stuff.
The first step for anyone in approaching their Y2K problems is to come up with
a plan of attack; ours is the one outlined in The Y2K
Problem, UIC, and You, and is detailed on the UIC Year 2000 Web site at
ACCC Y2K STATUS,
under UIC CAMPUS
The most important part of any Y2K project is the "make a list" step --
you clearly can't fix any system that you don't think of checking.
- Take the Year
Make a list. List every piece of hardware,
every software package, every hand-built program and macro, every embedded
system, and every data set that might be affected.
Organize the list. Are we going to throw this
out or replace it before the year 2000 will become a problem? Whose responsibility
is it to do the testing and provide the fix for this -- ours or the vendors?
How important is it? How long will it take to fix?
Research, test, fix, and retest.
The responsibility for generating the ACCC Year 2000 systems list is
roughly organized by group within the ACCC:
The ACCC Y2K system lists on the UIC Year 2000
Web site include the current Y2K status of ACCC-supported systems.
the UIC campus network and the ACCC dialin lines, both hardware and software
UIC telephones, voice mail, and pagers, including all hardware, software,
networks, and billing
ACCC-supported online communications packages and servers
ACCC-supported databases, computer accounts and billing, some electronic
mail servers and services, Web servers and services, and some UNIX software
personal computer labs, both software and hardware; printers in general
and printing from the labs; and ACCC Novell network services, both hardware
hardware, software, operating systems, and services on borg, tigger, icarus,
and a number of UNIX service machines, including the machines that provide
UIC electronic mail services
Because the UIC community, both as a group and as individuals, has so much
to consider, we have formed a UIC Year 2000 Committee; our email address
is given below. There's also UIC2000-L, a UIC Year 2000 email discussion
list that we hope will provide a campuswide forum for the discussion of
Y2K questions, where people will share their Y2K problems and solutions.
To subscribe to UIC2000-L, send an email message to firstname.lastname@example.org
containing this single line in its body:
subscribe UIC2000-L Your Name
As we said when we began this series of articles, individual Y2K problems
are often pretty easy to fix -- the problem is finding them all before
something breaks. If you have any questions or comments about the Year
2000, or, in particular, any ideas about things we may have overlooked,
please let us know.
Comments are welcome; please send them to
UIC Year 2000 Group, UIC2000@uic.edu