×
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.
Correct. That's why using the QSHEXEC command from my QSHONI wrapper is nice.
You will get all the useful return info. And you can write it to an OUTFILE, IFS, Job Log or Print File or all the above at the same time. (Overkill)
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 4
date: Fri, 4 Aug 2023 13:38:45 +0000
from: Buzz Fenner via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: Re: QSH Messages
On Thu, 3 Aug 2023, Richard Schoen wrote:
subject: Re: QSH Messages
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.
Yep. The 255 for the exit status apparently is just a catchall value.
--Buzz
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
