Re: QSH Messages -- MIDRANGE-L

Subject: Re: QSH Messages
From: Richard Schoen <richard@xxxxxxxxxxxxxxxxx>
Date: Thu, 3 Aug 2023 18:01:07 +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>

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!

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSH Messages , Niels Liisberg

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.