Still more fun for DGIs...greenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread
More fun for the entire family - watch as the witless prognostications of the Cult of GI go POOF!
-- Y2K Pro (email@example.com), March 29, 1999
As many as 13 states had non-compliant unemployment insurance systems as January 1999 began. These states were expected to have problems in January, because the newly unemployeed signing up for benefits would have an end date for benefits of January '00.
What happened and how was it dealt with? See this article from the Washington Post:
[sorry, the link to this article is now dead]
[bold emphasis mine]
13 States, District Face Y2K Problems
Unemployment Checks May be Slowed
By Stephen Barr
Washington Post Staff Writer
Wednesday, December 23, 1998; Page A03
Thirteen states and the District will have to put electronic bandages on their computers next month so they can pay new unemployment insurance claims into the year 2000, Clinton administration officials said yesterday.
The federal-state unemployment program provides one of the first large-scale examples of the problems caused by the "Y2K bug." Computer experts have warned that payments for billions of dollars in Medicaid, food stamps, child welfare and other federal-state benefits could be at risk because surveys have shown that states are moving slowly on the Y2K problem.
Many of the computer systems in the unemployment insurance program, which processes claims, makes payments to the jobless and collects taxes from employers, are more than 30 years old. The systems processed more than $20 billion in state unemployment benefits in fiscal 1998 and provide crucial data on economic trends.
Persons filing claims for jobless benefits are assigned a "benefit year," which means that -- starting Jan. 4, 1999 -- unemployment insurance systems will have to be able to process dates and calculations that extend into 2000. Y2K problems may occur when computers next month try to process a first-time claim with a benefit year that covers both 1999 and 2000, officials said.
Some states that have not solved their Y2K problems will use a simple temporary fix, such as ending all benefit years on Dec. 31, 1999, while other states will use different techniques that essentially trick the computers so they will perform accurate date calculations, officials said.
If the computers are still not ready to operate on Jan. 1, 2000, states then will rely on emergency backup plans, including the writing of benefit checks by hand, officials said.
John A. Koskinen, the president's adviser on Y2K issues, and Deputy Labor Secretary Kathryn Higgins yesterday stressed that the nation's unemployment insurance system would not suffer serious disruptions.
"A year out, we know where our problems are. . . . It's an enormous help to have that information," Higgins said.
Koskinen pointed to the contingency planning for jobless benefits as a clear sign that the government will be able to maintain important services and programs, even if computer systems encounter Y2K problems.
Labor Department officials listed Arizona, Connecticut, Delaware, the District, Hawaii, Illinois, Kansas, Louisiana, Massachusetts, Missouri, Montana, New Hampshire, New Mexico and Vermont as lagging on Y2K repairs. Puerto Rico and the Virgin Islands also are running behind schedule, the officials said.
Delaware, according to the Labor Department, will not have all computer systems converted until the last possible moment: Jan. 1, 2000. But state officials said the most critical systems have been fixed and suggested that even experts can disagree on how to assess Y2K readiness.
The District should have its unemployment system fixed by March 31, the Labor Department said.
Overall, the repair bill could run to $490 million for the unemployment insurance systems, according to preliminary estimates.
) Copyright 1998 The Washington Post Company
-- Kevin (firstname.lastname@example.org), March 29, 1999.
Y2K Prophylactic - maybe sysman isn't the only one that thinks you are a second grade dunce.
-- Wiseguy (email@example.com), March 29, 1999.