RE: Restricting Nosey Users Message Access

Chuck,

To secure a message queue from public browsing, yet still allow the
public to send messages to the queue, give *PUBLIC Data Add (*ADD), and
Object Operational (*OPR) rights.  This will allow any valid user to
send a message to a queue, but not to read, change, or delete messages
from that queue.


jte

--
John Earl | Chief Technology Officer
The PowerTech Group
19426 68th Ave. S
Seattle, WA 98032
(253) 872-7788 ext. 302
john.earl@xxxxxxxxxxxxxxxxxx
www.powertech.com 
 

--
 
Sorry if this is a repeat - I'm resending messages that appear to have
been lost today...


> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
> bounces@xxxxxxxxxxxx] On Behalf Of Chuck Lewis
> Sent: Tuesday, March 18, 2003 1:00 PM
> To: midrange-l
> Subject: Restricting Nosey Users Message Access
> 
> Hi Folks,
> 
> 
> 
> Have an interesting one here.
> 
> Users use Shift/Sys Req and option 5. Send a message to do quick
messages.
> 
> Well some of them have figured out that they can do 4. Display
messages
> and
> change the default of  *WRKUSR  to a valid User Profile name and see
other
> folks messages that are none of their business.
> 
> How can I restrict this ?
> 
> Thanks,
> 
> Chuck
> 
> 
> 
> 
> 
> _______________________________________________
> 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.