×
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, Jun 13, 2019 at 2:15 PM Kevin Adler <kadler@xxxxxxxxxx> wrote:
If you need to detect other PASE shells vs QSH, then trying to run
/QSYS.LIB/QSHELL.LIB/UNAME.PGM is one way, though I never particularly
cared for it (it was and still is a hack).
Not only is it a hack, it is more verbose and complicated than it needs to be.
I think it could be argued that pretty much any method you care to try
is ultimately hackish, but testing environment variables is at least a
simple and straightforward hack. And I would guess it's the closest
thing to an "official" method there is. There are definitely variables
that are present (by default) in a QSH session but not a QP2TERM
session, and vice versa.
John Y.
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.
midrange.com
