raithza wrote
15 years ago, everyone thought that software engineers in the 60's predicted that the world was going to end in 2000 because their calender systems couldnt handle that date....
I feel the need to put in a word here. Y'all can call me defensive if you like. I was heavily involved in the Y2k remediation program for a big, listed company.
A lot of people say that there was, in fact, never a problem because there weren't any failures (well there were, but nothing serious). There
was a Y2k problem, or perhaps problems plural. On the system that I remediated there was nothing that would have caused it to stop on the stroke of midnight, there was, however, a problem to do with years being represented as 2 digits (97, 98, 99 and then 00) that would have caused the system to get it's knickers into a severe twist when the first billing run of the new year happened.
There
was a Y2k problem. It's nature was simplified by the press (perhaps understandable) and things were over-sensationalised. Which may have been a good thing because it meant nobody could ignore it. So all over the world there were remediation programs to ensure that important systems (and this includes things like "smart" equipment in operating theatres, "smart" A/C systems and so on) would make the transition smoothly. Nobody sensible foretold the end of the world, but there were very real possibilities that companies would not be able to do business.
The IT community took the issue seriously, investigated and fixed the problems found.
Not a COBOL issue actually. COBOL was quite able to handle Y2k. However if poor design decisions had been made, irrespective of the platform/language, or programmers had sort to conserve memory resources that were comparatively expensive in the 70s or 80s by storing or representing the year portion of a date with 2 digits (a common portrayal of the bug) then there was the potential for a problem. In the system which I tested and fixed the operating system, database and programming languages were all themselves free of Y2k problems, but somebody had written some stupid code. More a human problem than a technology problem.