Teens maintained a mainframe and it went about as well as you'd imagine
- Reference: 1746433747
- News link: https://www.theregister.co.uk/2025/05/05/who_me/
- Source link:
This week, meet a reader we'll Regomize as "Serge," who, when he was just 16 years old, scored an amazing job: Working the night shift at a mainframe-for-hire company, alongside one of his friends.
"Our task mainly consisted of staying for the evening after the day staff had left, and running jobs that picked up data from the company's clients in other time zones," Serge told Who, Me?
[1]
Serge told us he and his friend worked with a DECwriter II, which he described as "a sort of printer with a keyboard attached, and no video monitor." A quick glance at The Centre for Computing History's [2]entry for the device shows Serge's memory remains accurate.
[3]
[4]
"We would type commands using the keyboard, and the computer at some remote location would send back the output to our commands, on paper," Serge explained.
That meant the system produced a literal paper trail, which their boss liked to review in the morning.
[5]
As you would when employing teenagers.
On busy nights, the DECwriter would exhaust its supply of paper. The boys were therefore shown the supplies store so they could feed the beast.
This system worked well until it didn't. One fateful night, Serge's pal forgot to get extra paper, panicked, and started shoving anything faintly paper-related into the machine – including cardboard.
[6]
The output was predictably dire, and Serge's pal fled the scene, leaving the mess he'd made for the day shift to clean up.
Which is how Serge found himself the only teenage mainframe wrangler at the company.
[7]What the **** did you put in that code? The client thinks it's a cyberattack
[8]Developer scored huge own goal by deleting almost every football fan in Europe
[9]Static electricity can be shockingly funny, but the joke's over when a rack goes dark
[10]Dev loudly complained about older colleague, who retired not long after
Serge tried to stay on the straight and narrow, but one evening a client called to request an extra item of data be included in an overnight job. Serge promised he'd sort that out, then forgot to do it.
"By the time I remembered, the last job had already been sent and it was already late in the evening," he confessed. "One option was to re-run the job and let it pick up the one record, which at 1,200 baud would take another hour."
The other option was to "abort the job, edit the file to add the missing record to the bottom, and then put it back in the run queue."
Serge thought he could pull this off, except for one small problem: Each record had a unique identifier. By this time, Serge had run enough jobs that he'd seen those identifiers followed a pattern that was almost sequential.
"I faked one," he admitted. "And naturally, all my work, including the clandestine bits, were recorded for posterity on the paper trail." The next day, Serge's boss and another even more senior manager greeted him.
"The only thing that prevented me from running for the door or bursting into tears was that the latter had a bit of a gleam in his eye, and a smirk on his face." He took that as a good sign and sat down demurely.
"Did you do this?" asked the senior manager.
Serge admitted he had done so.
"That was clever," came the reply. "But don't do that again."
Serge promised not to and kept his job.
Have you hired kids and regretted it? If you have a good story about this sort of thing, don't regret holding onto it and [11]click here to send an email to Who, Me? We love reading your tales and hope to feature many more on future Mondays. ®
Get our [12]Tech Resources
[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/columnists&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aBiMPUJ5ZU5Lj5W_81RGIAAAANU&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[2] https://www.computinghistory.org.uk/det/3367/Digital-DECWriter-II/
[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/columnists&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aBiMPUJ5ZU5Lj5W_81RGIAAAANU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/columnists&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aBiMPUJ5ZU5Lj5W_81RGIAAAANU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/columnists&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aBiMPUJ5ZU5Lj5W_81RGIAAAANU&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[6] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_offbeat/columnists&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aBiMPUJ5ZU5Lj5W_81RGIAAAANU&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[7] https://www.theregister.com/2025/04/28/who_me/
[8] https://www.theregister.com/2025/04/21/who_me/
[9] https://www.theregister.com/2025/04/14/who_me/
[10] https://www.theregister.com/2025/04/07/who_me/
[11] mailto:whome@theregister.com
[12] https://whitepapers.theregister.com/
At 60 character sparks per second? Unlikely.
Off topic but I misread as Have you had kids and regretted it?
DECwriter II
I remember entering a LISP assignment late on evening using on of those (all the VDUs [CRT] as usual were taken.)
My efforts worked 100% first time a circumstance that must have had cosmic significance as on leaving the lab I noticed the full moon was extremely dull and orange. A lunar eclipse. ;)
Like Serge I had a night job looking after a [1]HP3000 MPE minicomputer and HP1000. After a power outage and UPS missing in action had to bring up the 3000 from toggling the row of front panel switches (top right in image) to enter the bootstrap into memory right through to multiuser.
Knew nothing of this stuff until then but locating the manual and the (over)confidence of youth, I pulled it off but unfortunately probably doomed me to a life of BoFHry but then defenestration and unreported basement interments are among the perks.
Needless to say after moving on I avoided HP kit, MPE and promptly forgot SPL but looking back the system was probably quite advanced for its time. The command lines were extremely verbose I recall something like listUserCatalog against DIR or ls but possibly the system manager had configured it in moron mode as the capabilities of the entire user base were rather 'limited' in just about every sense.
[1] https://upload.wikimedia.org/wikipedia/commons/e/e3/HP_3000_Series_III.jpg
DECwriter
We had a DECwriter as the console on a VAX 11/750 running Berkeley unix. Every minute a cron job printed the date so that we could tell when any output had happened.
One day we suddenly started getting an error for every command - something like "out of processes". We found that the console had run out of paper, and several hundred "date" processes were stuck waiting for their output to complete.
> "Did you do this?" asked the senior manager.
He should have blamed it on a power serge...