On the other hand, it survived Y2k just fine

This big retail chain wants to make sure it doesn't feed duplicate orders into a mainframe system, so it tasks a Cobol programmer with making sure that doesn't happen, reports a pilot fish in the know.

"This was 1992," fish says. "The program would check for a duplicate order based on the order numbers stored in a table. There was a subscript just after the table that was used to step through the table to compare all the values.

"Unfortunately, he forgot to put a check in place to abort the process if the table got full.

"I had always heard that the worst bugs are found within six months after a program is put into production, and have lived with this notion secure in my mind.

"In 2014, my buddy who still works there told me that the program ordinarily took a few minutes to run, but one day it ran for two hours. They canceled it and quickly found this bug.

"So much for the six month rule."

Tell Sharky your story anytime. Send me your true tale of IT life right now at sharky@computerworld.com. You'll get a stylish Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.

Get your daily dose of out-takes from the IT Theater of the Absurd delivered directly to your Inbox. Subscribe now to the Daily Shark Newsletter.

To express your thoughts on Computerworld content, visit Computerworld's Facebook page, LinkedIn page and Twitter stream.
Windows 10 annoyances and solutions
Shop Tech Products at Amazon
Notice to our Readers
We're now using social media to take your comments and feedback. Learn more about this here.