Re: Suppressing job completion messages

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Hey, is the problem that the users message queue is in break mode and they
don't want the interruption for that message?  Then change the mode.  Or
specify a higher severity.
CHGMSGQ MSGQ(MYMSGQ) DLVRY(*BREAK) SEV(01)
CHGUSRPRF USRPRF(MYUSER) MSGQ(MYMSGQ) DLVRY(*BREAK) SEV(01)

Had an operator who insisted on break mode.  Then she never used
that session and kept it minimized.  Just how useful was that?

Most of our users never check messages.  It's up to GO CLEANUP to remove
them.  If a job is stuck in MSGW we get notified by messaging software.
We'd rather do that than have users try 'C' for Continue.


On Fri, Mar 17, 2023 at 6:41 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> 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
> completion?
>
> --
> JHHL
> --
> 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,
> 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.