I have had a read through of the manual for the IBM terminals of the time ( i had nothing better to do that day in work )and it does imply that this is the case as if there is a problem on the mainframe and its not taking input the solenoid does not fire even if its turned on .
Beam Spring IBM 3278 A02 restoration
-
- Location: UK
- Main keyboard: Filco ZERO green alps, Model F 122 Terminal
- Main mouse: Ducky Secret / Roller Mouse Pro 1
- Favorite switch: MX Mount Topre / Model F Buckling
- DT Pro Member: 0167
- Halvar
- Location: Baden, DE
- Main keyboard: IBM Model M SSK / Filco MT 2
- Favorite switch: Beam & buckling spring, Monterey, MX Brown
- DT Pro Member: 0051
I don't think it could have been waiting for the actual host because, as I understand it, the 3270 protocol wasn't realtime like a VT100 is, but more like today's web forms: the host sent a page to the terminal with fields to fill, the user filled the page, and the user input was returned to the host in one package.
But of course there must have been some intelligence in the terminal that handled this buffering and maybe also worked the solenoid.
@Tom: I didn't get it yet, but I'm not worried yet.
But of course there must have been some intelligence in the terminal that handled this buffering and maybe also worked the solenoid.
@Tom: I didn't get it yet, but I'm not worried yet.

- Muirium
- µ
- Location: Edinburgh, Scotland
- Main keyboard: HHKB Type-S with Bluetooth by Hasu
- Main mouse: Apple Magic Mouse
- Favorite switch: Gotta Try 'Em All
- DT Pro Member: µ
A levels boosted version of Halvar's picture of his A02. For no immediately apparent reason…
I'm using it in the DTA nomination for these keyboards, and need a URL!
I'm using it in the DTA nomination for these keyboards, and need a URL!