On Tue, Oct 3, 2023 at 11:45 AM Gerald Magnuson
<gmagqcy.midrange@xxxxxxxxx> wrote:
It's only been like 35 years of me doing this. even back in the dumb
terminal days, where the device could have 2 twinax addresses, so with the
secondary job you could have 4 sessions going.
In the dumb terminal days, secondary sessions were immensely valuable,
verging on essential.
I got used to them too, so much so that when I eventually got to a job
that used Client Access, I made macros to automatically log in, do
SYSREQ 1, and log in again. That way I would avoid the situation you
describe of having to do an unexpected and unwanted login.
But I am here to tell you that it's time to switch to using multiple
single-session tabs. Yes, it can take a while to rid yourself of the
SYSREQ 1 habit, which is deeply ingrained in muscle memory. But it is
worth it.
Some things to consider:
1. You can have more than just two sessions in a single window.
2. You can switch between (cycle through, if more than 2) sessions
with Ctrl+Tab. Replace your SYSREQ 1 muscle memory with this.
2a. If using more than 2, set up your hotkeys so that Ctrl+1 jumps to
the first session, Ctrl+2 jumps to the second, etc.
3. In the SYSREQ 1 arrangement, one of the sessions has to be
suspended; only one can actually *run* at any given time. And the
suspended one still holds onto locks. Multiple tabbed sessions are
fully independent and can run concurrently.
Good luck!
John Y.
midrange.com
