× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

i'll just throw this out there.

one of the guys in our team uses group jobs.
I have not gone that way, I'm more of a "new tab" kind of guy.

Reading the help is looks like sysrqs-1 on steroids

The Transfer to Group Job (TFRGRPJOB) command suspends the job that
issued the TFRGRPJOB command, and the group job specified by the
Group job (GRPJOB) parameter is resumed (if it already exists) or is
created (if it does not exist). In both cases, control is
transferred to the job specified by the GRPJOB parameter. The job
issuing the TFRGRPJOB command remains suspended until control is
passed back to it and the job is resumed.


John Yeung wrote on 5/3/2023 1:51 PM:
I am one of those very long-in-the-tooth users of SYSREQ 1 to flip
between two sessions in a single emulator window. Got very used to it,
muscle memory and all that. And it was close to essential back in the
day, when I was using an actual terminal that looked something like


It was by far the most convenient (if not only) way to have two
sessions open at the same time. Back then.

Well, I am now finally making a genuine effort to change my workflow
to make use of the relatively new tabs feature of the ACS emulator.
This is much better than SYSREQ 1 for probably a lot of reasons, but
the single biggest one for me is that all of them can be active

Lately I have been running into issues with the SYSREQ 1 arrangement
because whichever one is not being displayed is suspended. Which means
it gets no CPU time at all. Which, crucially, means it cannot release
any locks.

Back in the day, that wasn't a big problem for me. I got used to
making sure one session wasn't locking anything needed by the other
session before switching over. It was relatively straightforward then,
because I was only dealing with old-school means of working with
files, and RCLRSC was sufficient to release anything that an errant
program was holding onto. Now, with SQL keeping cursors dormant but
open even after you've explicitly closed them, it's not always so
straightforward. (See my other thread on releasing member locks.) With
multiple sessions independently active in tabs, "pseudo-closed"
cursors can be released without muss or fuss.

And having them in tabs in a single window is a bit nicer than each in
its own window because it's easier to navigate and organize sessions
in the SYSREQ 1 style. For example, if you're connected to three
different systems, each with two sessions; you can have three windows,
each with two easily switchable tabs, rather than six independent

If you're already using the tabs feature, thank you for indulging my
braindump. If you're using strictly one session per window and are
happy with that, wonderful. If you're still using SYSREQ 1, hopefully
I've exposed you to something that can improve your workflow.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.