Stuff is happening alright.. but just not enough to be beyond the scope of our capabilities to fix it in a timely fashiongreenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread
I work for a government agency, quite a large one at that. To date we have had some 4 systems with Y2K problems. Some are very small, i.e. the HVAC systems at some of our facilities had a problem. In other instances we've had problems with some of the data exchanges between our own distributed systems affecting as many as 200 of our sites. Because of the power of networking and our Warroom is on top of it, the programmers have been working on it for the last two days. I expect it will be remedied this week. Thanks to all who have been working 7/24 to catch these things. Please don't think there weren't any problems. Some of these are going all the way to the top...
-- slammer (Billslammer@yahoo.com), January 03, 2000
That's exactly the scenario that Flint had been projecting for so many months now. As I sit here at the computer, with uninterrupted electric and phones, it looks like Flint had this pegged much more accurately than I did. Flint, you took a lot of flack and hung in there. You are one tough cookie, my man, and I congratulate you.
-- Gordon (email@example.com), January 03, 2000.
GOOD MORNING Gordon!!! You may not believe this but I just poured my first cup of coffee and was thinking about *you* (along with a few others I haven't seen for awhile)! Wondering how you've been and if you had been monitoring the forum.
Yes Flint may have been much closer to the target than I was as well. He just didn't have kids living with him. Mothers take no chances. Far too many did. Time will tell, no wasted preps or regrets AT ALL! Hope all is well with you and Happy New Year!
-- Will continue (firstname.lastname@example.org), January 03, 2000.
Just a follow up. We encountered a problem late sunday afternoon with a data acquisition system that acquired and distributed volume information on processing throughputs for daily reporting. This was a "believe it or not" struct tm problem. This in turn cascaded through at least four other systems causing them to produce incorrect report. Here is the textbook case. One line of code bringing down 4 systems besides the original feeder system, and a host of other "shadow" systems (those created by individuals in the field mining data). Fix is in but deployment is the problem. Other systems on our mainframes also having some date reporting problems. Programmers attending. Looks like will be a Fix on Failure in 2 or 3 days. Anybody have similar warroom stories for the record..
-- slammer (Billslammer@yahoo.com), January 03, 2000.
Will continue probably expresses it as well as anyone ever could: It was never the odds, it was always the stakes. Something that Flint could not, can not, nor ever will be able to comprehend.
Meanwhile, I would not be so quick to pronounce anything to be a done deal yet. Still need to get through today (a big one), this week (should be very telling), and a few to come, before we can really say what the Y2K story was really all about.
Hoping for the best!!
-- King of Spain (email@example.com), January 03, 2000.
Excellent - from KOS - it was never the odds, it was always the stakes! That's it exactly!
-- Sheri (firstname.lastname@example.org), January 03, 2000.