|
Mark is correct. Note, though, that one could change the SEV parameter
and the SEV parameter on the CHGMSGQ command to cause such an effect.
(I don't recommend this, though, without a study of what else might be
affected by such a change.)
++
Dennis
++
"The problem with being punctual is that nobody's there to appreciate
it."
-- Franklin P. Jones
Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++
"Mark S. Waterbury" <mark.s.waterbury@xxxxxxxxxxxxx> wrote:
Hi, Jeff:
*BREAK vs. *NOTIFY is an attribute of the message queue, and not the
individual message.
However, you might want to take a look at the SBMJOB command MSGQ
parameter -- this allows you to control what message queue those
completion messages are sent to, for a given job, at the time the job
is
submitted.
HTH,
Mark S. Waterbury
On 8/29/2011 1:10 PM, Jeff Elam wrote:frequently now.
I have a couple of batch jobs that are being submitted quite
I'd like to change these two batch jobs so that the job completednormally
message doesn't pop up as all of our users have *break in the userprofile
for messages. I'd like it to stay *break for all other jobs butthese two.
Is there a way to change certain batch jobs so the completionmessages are
*notify only?--
Thanks,
Jeff
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.