To: Cheeky Kid who wrote (6271 ) 7/3/1999 8:58:00 PM From: J.L. Turner Read Replies (2) | Respond to of 9818
"The glitches were troublesome because they appeared in large mainframe applications that had ALREADY been certified as ''Y2K-compliant,'' meaning they were already thought to be prepared for the date change." What say you Cheeky? By Ross Kerber and Heather Kamins, Globe Staff and Globe Correspondent, 07/02/99 assachusetts state computers suffered a few glitches yesterday as fiscal year 2000 got under way, but officials said they remain comfortable with the progress of work to overcome the software problem known as the Y2K bug. The start of the new fiscal year in Massachusetts and 45 other states yesterday was seen as a key test of progress in work to protect against disruptions come Jan. 1, 2000. But the date change seemed to go unnoticed in most states and many municipal agencies. In Boston, information systems director Bill Hannon said city computers worked without a hitch despite a new software package that had just been installed. ''We fired it up at 8 a.m. and it's been fine,'' Hannon said. Cambridge and Quincy city officials also reported smooth operations, and errors seemed rare nationwide as well. ''Nobody had any issues at all, that I know of,'' said Gloria Timmer, executive director of the National Association of State Budget Officers, which surveyed many members yesterday afternoon. ''It was a good sign'' that most state remediation plans are on track, she said. The so-called Y2K problem relates to software applications that use only the last two digits of each year to keep track of the date. Left unrepaired, such programs might misinterpret the last two digits of Jan. 1, 2000, and cause systems to malfunction or shut down. To prevent that outcome, Massachusetts state agencies are spending $103 million to upgrade programs. Mostly those efforts prevented major problems yesterday, said Val Asbedian, an official in the state's division of information technology who is monitoring Y2K preparations. But exceptions were discovered at a state computing center in Chelsea, Asbedian said. One application used to track legislative action on a mainframe apparently misinterpreted the ''00'' of the new fiscal year as a previous date. In a second case, Asbedian said, a mainframe program wasn't able to allocate costs properly because of the unfamiliar year. Asbedian said he couldn't provide more specific descriptions of the problems, but said they were quickly spotted and repaired. The glitches were troublesome because they appeared in large mainframe applications that had already been certified as ''Y2K-compliant,'' meaning they were already thought to be prepared for the date change. But Asbedian said he was satisfied the two problems didn't indicate broader weaknesses in the state's remediation work. This story ran on page C2 of the Boston Globe on 07/02/99. © Copyright 1999 Globe Newspaper Company.