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



I forgot to mention that we have a working method for getting SMS
notifications in case
of certain MSGs (CPFXXX and other) occur.
It is done by starting several STRWCH jobs in QSTRUP that watch for MSGs I
deem
important
(I developed it initially to be notified in case a nightly batch.job
"Bombed")
When such a MSG occurred a watch programm sends a mail to an external
mail-to-SMS service.


Gad






date: Wed, 29 May 2024 11:34:02 -0400
from: Rob Berendt <robertowenberendt@xxxxxxxxx>
subject: Re: QSYSOPR MSGs

Yes, doing the CHGUSRPRF will alienate the user from his own message queue.

On Wed, May 29, 2024 at 1:41?AM Gad Miron <gadmiron@xxxxxxxxx> wrote:

Thanks Patrik, Rob

I failed to mention that the user should receive both QSYSOPR MSGs
AND his own MSGs.

I think that issuing CHGUSRPRF USRPRF(UserA) MSGQ(QSYSOPR)
will alienate the user from his/her own MSGs.

Right?


Gad



from: Rob Berendt <robertowenberendt@xxxxxxxxx>
subject: Re: QSYSOPR MSGs

Options include:

User permanent
CHGUSRPRF USRPRF(SAMPLE) MSGQ(QSYSOPR) DLVRY(*NOTIFY)

Job level:
CHGMSGQ MSGQ(QSYSOPR) DLVRY(*NOTIFY)

Either could use *BREAK instead of *NOTIFY. Experience has told me
those
users who insisted on *BREAK soon stop using that session because it's
irritating as it keeps interrupting their work. Now they get no
notification in their current session. But heaven help you if you ask
them
if you'd rather you change them to just *NOTIFY. Odd, but true.

Other options include a message monitoring solution which sends them an
email. Commercial solutions are available which allow you to taylor
it a
bit more based on severity, message content, etc. You can roll your
own
if
you'd rather.


On Tue, May 28, 2024 at 12:58?AM Gad Miron <gadmiron@xxxxxxxxx> wrote:

Hello guys

Is there a way to have a user receive QSYSOPR MSGs?
(setting the user class to *SYSOPR does not do the trick)


TIA
Gad


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






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