Re: Suppressing completion messages on batch jobs -- MIDRANGE-L

× 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.

Subject: Re: Suppressing completion messages on batch jobs
From: Marc Rauzier <marc.rauzier@xxxxxxxxx>
Date: Mon, 6 Jun 2022 18:53:10 +0200
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>

Le 06/06/2022 à 18:14, James H. H. Lampert via MIDRANGE-L a écrit :

Can somebody please refresh my memory:

Is there an easy way to set a batch job to *not* issue a completion message unless something goes wrong?

Or to just *not* issue a completion message, period?

If you have access to submission program, use SBMJOB MSGQ(*NONE) maybe?

Or for a given user profile and because SBMJOB MSGQ(*USRPRF) is the default, set user profile with CHGUSRPRF DLVRY(*HOLD)? However, this will apply to all messages sent to the user message queue whatever could be the sender.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

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.