The question I have is: Why would you want to? How would you know if a
job actually ran? Some user complains they didn't get their report, or
a job setting up some files, etc., runs or not the only way being to
look at the completion messages...


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of James H. H. Lampert via MIDRANGE-L
Sent: Friday, March 17, 2023 3:42 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Suppressing job completion messages

I've just been asked whether it's possible to suppress completion
messages on batch jobs that end normally.

To my great surprise, I found that one could use MSGQ(*NONE) on the
SBMJOB command.

But that suppresses *all* messages. If the job hangs, with a QSYSOPR
message, nothing gets back to the user who submitted the job, to
indicate that it's waiting on a QSYSOPR message.

Is there something a bit less drastic? That would only suppress normal

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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