I remember trouble shooting a user's twinax terminal, session would drop intermittently, monitor screen would shake, other weird items.
Problem was old knob and tube wiring in the wall, to close to the terminal/monitor. Moved the terminal/monitor 1 foot, problem went away.
Paul
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Patrik Schindler
Sent: Tuesday, May 25, 2021 8:49 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Dedicated console
Hello Rob,
Am 21.05.2021 um 19:37 schrieb Rob Berendt <rob@xxxxxxxxx>:
Someone replacing a terminal on the same line and forgetting to change the port number from 0 caused issues.
This is as dumb as replacing a SCSI drive and not checking the SCSI ID. I don't feel this is a twinax fault.
Baluns stretched between multiple buildings was an issue.
I'd have opted for a separate controller, being connected via SDLC to the main machine, and having twinax ports for local terminals and printers.
Either way, it is dead and gone and time to move on.
In the commercial world, you're (mostly) right. ;-)
When in these days of virtual machines not even vm based pc clients and servers have their own keyboards and displays it's time to accept it.
Yes, but they have virtual "terminals" (RDP clients, ssh-clients), and a virtual console. Not much different as in the i world.
Oh, and the vm server? The closest thing it has to a physically attached keyboard and monitor is a KVM shared between numerous devices.
On huge installations, maybe. Where I work, we have just eight VM servers, and rack space in the colocation center is too precious to be wasted with displays. They offer a rollable table with keyboard, mouse, and display, but this is thought for emergency use.
Often, modern servers have a separate management entity for access with browsers or ssh, to switch the machine off and on, provide remote install via emulated install devices, and of course a virtual display and keyboard. Completely sufficient as long as IP and network works.
:wq! PoC
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
