×
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 Fri, Aug 4, 2023 at 10:20 AM Richard Schoen
<richard@xxxxxxxxxxxxxxxxx> wrote:
Niels, you are correct on STDERR, however believe that QSH mixes STDOUT and STDERR together. Correct me if I'm wrong on that.
That is correct in a sense. Typically both of those streams "point to"
the same output device. That's the most convenient thing to do for the
usual scenario where a user is typing in commands at a command line,
and both "normal" and "error" output is being shown on the screen.
That's probably the best option for the QSH interactive "shell"
environment (which is meant to mimic a Unix shell, after all). If it
could be translated to a more IBM i "CL prompt" way of doing things, I
think STDOUT would go to the screen and STDERR would go to the job
log.
John Y.
As an Amazon Associate we earn from qualifying purchases.
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.