× 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.



On Thu, 2015-10-08 at 16:03 -0400, John Yeung wrote:
On Thu, Oct 8, 2015 at 12:59 PM, Justin Dearing <zippy1981@xxxxxxxxx> wrote:
They're both different animals, and as a user of PASE and QSH, which POSIX
standards it follows are really not my benchmark. I'd rather frame it like
this:

I agree with all of that. I was trying to say that "standards" wasn't
a useful way to talk about it.

Your original message mentioned QSH and Qshell. These two terms refer
to the same thing, but "Qshell" is just for verbal or prose use, while
there is an actual QSH command. The analogy for Unixy folk would be

QSH : Qshell :: sh : Bourne shell

Note that the QSH command can also be spelled STRQSH.

I don't know all the answers to the specific points you brought up,
but in my view (as a former Unix user and still something of a fan),
someone who is very proficient in some flavor of Linux or Unix will be
"annoyed but comfortable enough" with either QSH or QP2TERM for
certain shell tasks. Probably QP2TERM will be the less annoying of the
two, but both of those are still fundamentally 5250 green-screen
interfaces, so don't expect to do typical stream-style console-based
interaction. In other words, definitely nothing like curses, and even
a lot of basic "interactive" stdin/stdout/stderr stuff will be broken.
For example, the 'more' command is almost completely broken (good luck
reading anything other than the first page with it). Anything that
can't just run to completion without user intervention is basically
unworkable on either QSH or QP2TERM.

I'm curious as an aside...

Can you ssh, or term, "into" pase so bypassing the green screen
entirely?

If you can, does it then behave in terminal fashion so curses and/or
x-11 (is that the correct term?) works as expected in a manner that us
Linux bods would understand with a form of "windowing" (curses style)
and/or standard sh style input-output such as "| more" and wait for
input in a running shell script?


In case the distinction was not clear, QP2TERM and PASE are not the
same thing, though the shell that opens up when you call QP2TERM runs
in PASE.

John Y.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2024 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.