The IBM System/360 Model 40 told you to WHAT now?

When a software update reveals what you really think

Who, Me? A Register reader is tripped up by the curse of software updates decades before Patch Tuesday was a twinkle in Microsoft's eye. Some things never change. Welcome to Who, Me?

Our story this week comes from "Ivor" courtesy of his experience with punched cards and the IBM System/360 Model 40.

This particular bit of kit was aimed at businesses that had outgrown more simplistic hardware. There were rows of lights, magnetic tape, and dryer-sized magnetic disk units. CRTs had yet to make an appearance at Ivor's facility, but punch cards were still in use for programming purposes.

And output? Via a typewriter that chugged along at around 12-15 characters per second.

After spitting out whatever message it needed to, the computer would use the typewriter to punch out "READY FOR COMMUNICATIONS" – informative, yes. Performant? Not really. Not when one considers how many times per day the operators were presented with the message.

"Luckily," said Ivor, "at that time in their history, IBM provided the operating system as a box of punched cards (source code) that were assembled into executables and so for those interested, one could replace a few or many punched cards and modify the operating system.

"There were magazines that published code modifications for various improvements and as a junior assistant system administrator, a code update that would reduce the operator message to something shorter seemed like a great improvement."

So the next time the system was updated, Ivor made a change. The message text got updated and, in a different module, the length in the print command was set to two.

"Operations staff loved me," he recalled happily, "as now they were presented with 'GO' instead of the lengthy previous status message."

Months went by. Ivor moved on to other projects. He was therefore unprepared when the inevitable phone call came in.

It transpired that something odd had happened to his message. Software updates, you see, were issued every six months and somebody had helpfully fed them into the computer. One update was to the module responsible for printing the status message, effectively backing out of Ivor's two-character speed up.

The operators were a bit alarmed by the output.

"What the hell is that?" demanded the datacenter manager, pointing to the console typewriter.

Ivor peered at the page. Instead of just a cheery "GO", the entire message had been printed. And Ivor had been a very naughty boy indeed.

The "GO" was still there, but was followed by a strongly worded suggestion (in deference to more delicate eyes) that the operator might like to, er, go away.

The message had been repeated over and over again.

"It seems the latest update had replaced the print command with one with the original message length, but my replacement message which had never seen the light of day due to a truncated print command message length was now exposed to all."

Ah, the delight of receiving a call when a long-forgotten bit of code explodes in a user's face. Would you have hurriedly solved the problem, or adopted a funny voice and pretended the caller had dialed a wrong number? Confess all with an email to Who, Me? ®

Similar topics

Broader topics

Other stories you might like

  • September 16, 1992, was not a good day to be overly enthusiastic about your job
    If I get in early and work hard, everyone will notice, right?

    Who, Me? "The early bird trashes the business" is a saying that we've just made up, but could easily apply to the Register reader behind a currency calamity in today's episode of Who, Me?

    Our hero, Regomized as "Mike", was working as a "data entry operative" for a tourism company in 1992. The company ran bus tours to the then brand-new EuroDisney, parent company of Disneyland Paris (now the most visited theme park in Europe), which had opened earlier that year.

    Mike was an eager beaver, his youthful naivete having convinced him that if he worked extra hard, came in extra early, and kept the in-tray clear, then his efforts would be both noticed and rewarded with promotion and a bump in pay.

    Continue reading
  • An international incident or just some finger trouble at the console?
    All routers are equal, but some are more equal than others

    Who, Me? Welcome to an edition of Who, Me? where some configuration confusion left an entire nation cast adrift.

    Today's story is set in the early 2000s and comes from a reader Regomized as "Mikael" who was gainfully employed at a European ISP. The company had customers in multiple countries and Mikael's team was responsible for the international backbone.

    "Us senior network engineers were widely regarded as consummate professionals," he told us, before adding, "at least amongst ourselves."

    Continue reading
  • A discounting disaster averted at the expense of one's own employment
    I know what this process needs: Microsoft Access!

    Who, Me? A tale of discounts and process improvement via the magic of Excel, Access and a fair bit of electronic duct tape we imagine. Welcome to Who, Me?

    "James" is the Regomized reader of record today, and continues the theme of running the risk of doing a job just that little bit too well with an ancedote from the end of the last century involving his first job out of university, at a certain telecommunications giant.

    The job involved a process of calculating the discount received by big customers (the ones with multiple branches). "For the life of me I can't remember what the main DB was called," he told us, "but it was the old style green writing on a black screen that took forever to download the necessary data."

    Continue reading
  • In IT, no good deed ever goes unpunished
    When being helpful can mean being shown the door

    Who, Me? Going above and beyond in IT can sometimes lead to also going directly out of the door, as one Register reader found when discovering that sometimes efficiencies can be less than rewarding.

    A reader Regomised as "Will" told of us his days working at a now-defunct company that produced large telephone switches. In those days whenever a major software revision occurred, customers were expected to send in their configurations and Will's group would merge them into the latest and greatest. A new load would then be returned to the customers.

    It was not a fun process, not least because of constant hardware and software failures during the merge process. "When I first started, there was a constant grumble about how unreliable the machine used for the merging was," Will told us.

    Continue reading

Biting the hand that feeds IT © 1998–2022