× 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, 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 electronic mail transmission may contain confidential or privileged information. If you believe that you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.


------------------------------

message: 5
date: Fri, 4 Aug 2023 14:12:04 +0000
from: Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
subject: Re: QSH Messages

What did you try and what didn't work ? Elaborate.

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

------------------------------

message: 5
date: Thu, 3 Aug 2023 15:15:14 -0500
from: Brad Stone <bvstone@xxxxxxxxx>
subject: Re: QSH Messages

I've tried that and never gotten it to work.

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

------------------------------

message: 3
date: Thu, 3 Aug 2023 13:17:25 -0400
from: Rob Berendt <robertowenberendt@xxxxxxxxx>
subject: Re: QSH Messages

You're welcome.

On Thu, Aug 3, 2023 at 12:07?PM Buzz Fenner via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On Thu, 3 Aug 2023, Rob Berendt wrote:

Quickest way to find what message file has a message:
select *
FROM QSYS2.MESSAGE_FILE_DATA
where MESSAGE_ID='QSH0005'

Worked great, Rob. Thanks!



------------------------------

Subject: Digest Footer

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.



------------------------------

End of MIDRANGE-L Digest, Vol 22, Issue 662
*******************************************


________________________________

This electronic mail transmission may contain confidential or privileged information. If you believe that you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.


________________________________

This electronic mail transmission may contain confidential or privileged information. If you believe that you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.