Re: Qsysopr messages

[mcrump@xxxxxxxxxxxxxx]

I'm not 100% sure but you should be able to use data access of read, add,
and execute and user programs/users should be able to write and view
QSYSOPR but restrict them from removing messages.  Assuming this is what
you want to do.  You can modify the attention key screen (at least I
remember seeing some posts on that in the past), however using the object
security may be the easiest implementation.




wawrzaszek@austeel.com (Wawrzaszek) on 10/19/98 10:41:17 AM

Please respond to MIDRANGE-L@midrange.com

To:   "midrange" <MIDRANGE-L@midrange.com>
cc:    (bcc: Mike Crump/IS/Ball-Foster)

Subject:  Qsysopr messages




We are trying to stop a rather serious problem at our company.  Some users
have found out that system request 6 brings you to the qsysopr messages!
We do not want to take away system request, only using the 6 if possible.
Or is there another way to stop them.  I tried taking away authority to
qsysopr msgq but some programs need to write to that msgq so taking away
authority to it or giving them *use will not work.  Does anyone have any
suggestions?

Thanks in advance,
Angie Wawrzaszek

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---






+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---