Does anyone have evidence of failures occurring at the Fed level associated with the Fiscal Calendar: Oct 1st'99. Or did it pass without any affect on the system...

-- william holst (wholst@hotmail.com), October 04, 1999

Answers

See "real y2k failures over the weekend" I think its like 2 posts down from this one. With this only being Monday I suspect it may be a week or 2 before we see anything else.

Of course then there is the fact that its called the y2k problem.

-- David Lee Roth (Diver Down@Van Halen.ou812), October 04, 1999.

http://dailynews.yahoo.com/h/ap/19991001/tc/y2k_failures_1.html

[Fair Use: For Educational/Research Purposes Only]

Friday October 1 6:58 PM ET

Gov't Reports 2 Minor Y2K Failures

By TED BRIDIS Associated Press Writer

WASHINGTON (AP) - The Energy Department and National Science Foundation suffered minor computer failures blamed on the Year 2000 technology problem on Friday, the first day of the government's new fiscal year.

Both problems were solved by the end of the day, according to the President's Council on the Year 2000 Conversion, which planned to monitor agencies through the weekend for additional reports of problems.

``We thought we might have a handful of issues come up,'' said Jack Gribben, a spokesman for the council.

The Energy Department reported that a purchasing system temporarily failed, and the science foundation reported problems with a system that provides information to grant recipients.

The date system for many federal computers on Friday rolled to 2000 to mark the beginning of the government's fiscal year, offering an early taste of how the nation's computer systems may fare in the early hours of Jan. 1.

The so-called Y2K problem exists because many older computers and software programs recognize only the last two digits of the year and could mistakenly interpret ``00'' as 1900.

Nearly all states and many companies started their fiscal years in July. Few problems were reported then.

Though Friday was the first government-wide date challenge related to Y2K, there have been other tests in recent months: A date change in a satellite navigation system caused some failures, including problems in Japan, where thousand of drivers complained about the loss of their mapping computers.

Last month, Sept. 9 passed with no reports of serious problems, amid concerns that some older computers might interpret ``9999'' as a command to stop operating.

----------------------------------------------------------------------

-- Linkmeister (link@librarian.edu), October 04, 1999.

Your subject line is misleading----Last of the pre-y2k dates...

There's still, as of today: Oct,5,6,7,8,9,10,11......You get my point.

Y2k NOT y99.xk.....embedded wildcard gonna come up joker!

Don't ask me what that means, I gotta get some lunch.:)

-- CygnusXI (noburnt@toast.net), October 04, 1999.

william: This isn't Cinderella. The world isn't going to turn into a pumpkin at the stroke of midnight 010100. What's happening is a gradual slowdown of our digital efficiencies that will cluminate in an economic depression starting sometime next year. Oh yeah, and there's something called a "stock market crash" on the horizon also.

-- a (a@a.a), October 04, 1999.

Remember the zombie creed of denial as it comes to all predictions made. If you stop making the predictions then they were never made.

Congrats the @, nice to see more people will believe in Y2K TEOTWAWKI in 2010. Persitence is the key my friend.

-- THe Y2Idiot (thezombies@arepullingair.com), October 04, 1999.

THe Y2Idiot,

Before February 1st, I didn't know one way or another if the Jo Anne Effect was going to cause noticeable problems that would end up being reported. After February 1st, when Wal-Mart and some other companies entered their fiscal year 2000 with no reported problems, I realized that what PNG had been saying on this forum was true...that problems in accounting software aren't nearly as noticeable to outsiders as problems in manufacturing or distribution would be.

We won't hear that much about Y2K-related manufacturing or distribution problems until January 2000. It was clear to me in February that we weren't going to hear much about fiscal year rollover problems in accounting software on April 1st and July 1st. Most people on this forum weren't expecting "show-stoppers" on April 1st and July 1st either, but yet the issue of few reported problems does continue to get raised from time to time here.

Anyone who'd like to learn more about the significance and non- significance of fiscal year rollovers in accounting software, as well as find examples problems that have occured so far can find quite a few relevant links on the following thread:

"Significance of States Fiscal Start"

http://www.greenspun.com/bboard/q-and-a-fetch-msg.tcl?msg_id=00122f

Almost all non-accounting software problems, PC BIOS chip and PC operating system problems, and embedded system/process control system problems are still ahead of us. Those are the ones with the potential of being "show-stoppers."

It should also be noted that the GPS rollover and 9/9/99 were each their own unique types of glitches and are not a subset of the "99" and "00" problem that we usually refer to as Y2K.

-- Linkmeister (link@librarian.edu), October 04, 1999.

a,

Are you suggesting that failures associated with Y2K will accumulate and slowly degrade the system? I do not agree with that position as it applies to the Telecomm arena as it has been shown in the recent past that companies are quite capable and willing to rip out inefficient or faulty technology i.e., AT&T Wireless Services, Bell South, etc. In fact, our industry (Telecomm) is experiencing shorter product development timelines and greater demands from the customer in terms of functionality (and efficiency). Just 8 - 10 yrs ago no one believed that wireless commo would penetrate 30% of the population and start to compete with the wireline in terms of offered traffic. And yet, here we are talking about surfing the web and carrying video over wireless devices...I do not believe that the wireline/wireless network is going to be allowed to suffer death from a thousand cuts. Competion from existing and emerging technologies (ASDL, EDGE, LMDS, etc) will provide us with the necessary bandwidth to ride out any Y2k problems and allow for increased features/services in the immediate future.

-- william holst (w_holst@hotmail.com), October 04, 1999.

Two more minor failures have been reported.

http://dailynews.yahoo.com/h/ap/19991004/pl/y2k_failures_3.html

[Fair Use: For Educational/Research Purposes Only]

Monday October 4 7:25 PM ET

Government Reports Two Y2K Failures

By TED BRIDIS Associated Press Writer

WASHINGTON (AP) - The federal government reported two more minor computer failures blamed on the Y2K technology problem on Monday, days after the start of its fiscal year 2000.

The Justice Department and Federal Aviation Administration each reported problems with budget-related computers caused by the date rollover, but they were able to solve the failures within hours, according to the President's Council on Year 2000 Conversion.

The council, which monitored agencies through the weekend for reports of problems, earlier cited minor failures at the Energy Department and National Science Foundation. The fiscal year began Friday.

The Justice Department reported a problem with its financial management information system but was able to fix it by day's end, said Jack Gribben, a spokesman for the council. The FAA's national automated travel system also failed but was quickly fixed.

Gribben on Monday said none of the failures threatened public safety. The council asked agencies to continue to report problems through this week because failures could occur days or even weeks after Friday's date rollover.

``There may be some agencies out there that haven't tried to use a fiscal application for the year,'' Gribben said. ``We don't expect we are going to hear much.''

The Energy Department reported Friday that a purchasing system temporarily failed, and the science foundation reported problems with a system that provides information to grant recipients.

Gribben said it was unclear whether agencies had previously tried to repair those systems that had failed.

Most departments are close to finishing repairs on their most important computers, but some won't be able to complete work before Jan. 1 on systems that weren't designated ``mission critical.''

The so-called Y2K problem exists because many older computers and software programs recognize only the last two digits of the year and could mistakenly interpret ``00'' as 1900.

----------------------------------------------------------------------

-- Linkmeister (link@librarian.edu), October 04, 1999.