Mainframe error ruins a work week

In a recent installment of The Register's "Who, Me?" column, a reader known as "Mark" recounted an incident from his time at Sperry Univac, a prominent mainframe manufacturer. During this era, work was done using primitive technology like punch cards, with no monitors, where program results were sent directly to printers.

Mark described how his job involved managing inventory tasks that ran in "top memory," which was essential to prevent conflicts with other workloads. There were two printers available, allowing different workflows to generate hard copies simultaneously. However, an attempt to save paper led to an error that affected an entire week of work.

## Why it matters Stories like this remind us of how technology has evolved and how errors in legacy systems can have significant consequences. Mark's experience illustrates the challenges workers faced in the mainframe era and how decisions to optimize resources can backfire.

## What we know Mark's account serves as a clear example of the difficulties in managing computing systems in the past. The technological limitations and lack of modern interfaces made human errors more common and often more costly.

## What remains unclear The specific steps that led to the error ruining Mark's work week have not been detailed. Additionally, it is unclear how the company handled the situation or what lessons were learned from this experience.