Although we are now more than eight years beyond the end of 1999, system time glitches still threaten to interrupt smooth operation of software programs. This weekend marks the beginning of the 30-year countdown to the date beyond which some Unix systems cannot calculate, giving us one more opportunity to begin the 20th century all over again. While 2038 is well into the future, the problem may surface soon with software that calculates projections 30 years into the future (think mortgage calculators and investment models).

  The (relatively) smooth transition to the year 2000 illustrates the effectiveness with which most businesses and software providers met the technical challenge of the first Y2K scenario. While the Unix Millennium bug is perhaps even less difficult to overcome than its predecessor, it provides a poignant reminder of the continuing need to address such issues in technology contracts. While making specific reference to Y2K seems a bit antiquated, it is wise to consider how any representations and warranties in a given technology agreement would apply in these type of scenarios. It also provides a good opportunity to consider the extent to which a vendor is responsible for particular components of the purchaser's technical infrastructure.