Panic in the mailroom: The perils of an operating system too smart for its own good

That other 1973 hit: The Dark Side of the Mainframe

Who, Me? Modern life is rubbish, so take a trip back to the 1970s with a Who, Me? all about the Master Control Program (MCP).

Today's tale comes from a Reg reader we'll call "Simon." Our man was spending 1973 toiling away as a computer operator for an American city. The city was big enough to justify splashing some dollars on a new Burroughs B-6700 mainframe "and we were still learning the magnificent multi-cpu, multi-tasking operating system known as MCP."

It was heady stuff. The Burroughs B-6700 was an unusual beast; eschewing machine code in favour of higher level languages. ALGOL was a particular favourite, although application languages such as COBOL were on offer.

The operating system, the Master Control Program - not to be confused with the fictitious computer program villain from Tron - was also an innovation. Multiple programs could share the system and more than one processor could run programs. Now approaching 60 years since its initial release, vestiges of the OS can still be found lurking on the Unisys website in ClearPath MCP Release 19 guise.

Back in 1973, Simon was using the mainframe to run billing jobs for the city-owned electricity utility. "This generated 20,000 - 30,000 bills each night," he explained, "the billing program sent the output to a printer backup tape which was then printed using a system utility."

At this point, it is worth noting that a "feature" of this particular edition of the MCP was the automatic restart of certain system utilities after system fault and reboot.

"One of the restartables was the program that printed from printer backup tape..." said Simon, for whom the significance of this fact would become horribly clear.

On the night in question, Simon had been assigned the task of dealing with the billing for the electricity utility. The billing program had done its stuff, as it always did, and Simon was diligently returning the tapes to storage when the MCP abruptly fell over and the Burroughs restarted.

Only four people were on shift, and it was all hands to the pumps to get everything running again. Simon noted that the printer had restarted and gave silent thanks for whatever colleague had saved him the task of dealing with it. Once complete, he trotted down to the mailroom with the stack of printed bills.

Neither Simon, nor those in the mailroom that did the mailing, spotted that around 2,500 bills had been printed twice.

The customers, however, did.

"A few days later some people called the newspaper to report receiving two bills for that month," he said. "You really don't want to end up on the front page of the newspaper."

"Meetings were held. Much shouting and wailing and gnashing of teeth," he recalled. "Fortunately, the big boss wanted to squeeze concessions out of Burroughs that week so the blame fell on them for lack of documentation and training."

For Simon, things took a more surreal turn. Having had to endure a dinner of fingerpointing from his parents (who were also on the receiving end of twin bills) he discovered that a few of his fellow citizens took a city hall cock-up a little too seriously:

"Some wackadoodles were less forgiving. We received a bomb threat in the data centre a few weeks later."

Ever screwed something up so comprehensively that you've found yourself on the end of potential physical as well as verbal abuse? Or forgotten the perils of an unplanned restart? We've been there. Send an email to Who, Me? if you have too. ®

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