×
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.
Not to belabor the point, but if you use my QSHEXEC command you can run in batch and print the STDOUT log to spool file as an option.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 2
date: Fri, 4 Aug 2023 15:16:31 +0000
from: Buzz Fenner via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
subject: Re: QSH Messages
On Thu, 3 Aug 2023, Richard Schoen 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.
I'm submitting (SBMJOB) the command inside a CLP using QSH. I had the ENVVAR QIBM_QSH_CMD_OUTPUT set to log the output. However, the data un-readable using a regular text editor. Not sure where to go from here...
--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
