RE: QSH Messages -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: QSH Messages
From: Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
Date: Fri, 4 Aug 2023 14:19:56 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Niels, you are correct on STDERR, however believe that QSH mixes STDOUT and STDERR together. Correct me if I'm wrong on that.

Thanks

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------

On Thu, Aug 3, 2023 at 3:05?PM Niels Liisberg <nli@xxxxxxxxxxxxxxxxx> wrote:

just to continue Richard ....

STDOUT and STDERR - to be more correct.

On Thu, Aug 3, 2023 at 8:01?PM Richard Schoen
<richard@xxxxxxxxxxxxxxxxx>
wrote:

I don't think just getting the definition of the QSH0005 message is

enough

to know why your QSH/PASE job failed.

You need the STDOUT messaging from the program call.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSH Messages , John Yeung

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