Computer Old Farts Forum
 help / color / mirror / Atom feed
From: segaloco via COFF <coff@tuhs.org>
To: COFF <coff@tuhs.org>
Subject: [COFF] Typical Fate of Older Hardware
Date: Sat, 29 Jul 2023 23:26:21 +0000	[thread overview]
Message-ID: <gwg5D0OXd5pPt36UvyecqSfSPYzS_j3ngzMXmUHMf60rvSV5WgYt8cu1zCOjhVf4CzObWsgemYg5yqxVxDsluMpqMtUQeV5ZxvLjSX0n-4s=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]

Howdy folks, I wanted to get some thoughts and experiences with regards to what sort of EOL handling of mainframe/mini hardware was typical. Part of this is to inform what and where to look for old hardware things.

So the details may differ with era, but what I'm curious about is back in the day, when a mainframe or mini was essentially decommissioned, what was more likely to be done with the central unit, and peripherals if they weren't forward compatible with that user's new system.

Were machines typically offloaded for money to smaller ops, or was it more common to simply dispose of/recycle components? As a more pointed example, if you worked in a shop that had IBM S/3x0, PDPs, larger 3B hardware, when those fell out of use, what was the protocol for getting rid of it? Were most machines "disposed of" in a complete way, or was it very typical to parts it out first, meaning most machines that reached EOL simply don't exist anymore, they weren't moved as a unit, rather, they're any number of independent parts floating around anywhere from individual collections to slowly decaying in a landfill somewhere.

My fear is that the latter was more common, as that's what I've seen in my lab days; old instrumentation wasn't just auctioned off or otherwise gotten rid of complete, we'd typically parts the things out resulting in a chassis and some of the paneling going in one waste stream, unsalvageable parts like burnt out boards going in another, and anything reusable like ribbon cables and controller boards being stashed to replace parts on their siblings in the lab. I dunno if this is apples to oranges though because the main instruments I'm thinking of, the HP/Agilent 5890, 6890, and 7890 series, had different lifespan expectations than computing systems had, and share a lot more of the under the hood components like solenoids and gas tubing systems, so that may not be a good comparison, just the closest one I have from my own personal experience.

Thoughts?

- Matt G.

[-- Attachment #2: Type: text/html, Size: 2701 bytes --]

             reply	other threads:[~2023-07-29 23:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-29 23:26 segaloco via COFF [this message]
2023-07-30  3:04 ` [COFF] " steve jenkin
2023-07-30  3:33   ` segaloco via COFF
2023-07-30 16:15 ` Grant Taylor via COFF
2023-07-30 20:33   ` Steffen Nurpmeso
2023-07-31 16:36     ` [COFF] " Paul Winalski
2023-07-31 16:52       ` [COFF] " Brad Spencer
2023-07-31 18:40         ` segaloco via COFF
2023-07-31 21:20           ` Paul Winalski
2023-07-31 23:11             ` steve jenkin
2023-07-31 21:59           ` segaloco via COFF
2023-07-31 17:28       ` Steffen Nurpmeso
2023-08-01  6:30     ` Wesley Parish
2023-08-01 21:14       ` Steffen Nurpmeso
2023-07-30 21:51 ` Paul Winalski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gwg5D0OXd5pPt36UvyecqSfSPYzS_j3ngzMXmUHMf60rvSV5WgYt8cu1zCOjhVf4CzObWsgemYg5yqxVxDsluMpqMtUQeV5ZxvLjSX0n-4s=@protonmail.com' \
    --to=coff@tuhs.org \
    --cc=segaloco@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).