RE: Restricting Nosey Users Message Access

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Chuck, People need at least *ADD authority in order to send messages to a 
queue. For user profile message queues (in QUSRSYS usually), try 
restricting *PUBLIC to *ADD authority only--user usually has *ALL authority 
to it, as he/she should.

Workstation queues are different - unless you can guarantee that they only 
go to certain users. These are in QSYS. *PUBLIC is *CHANGE authority. Maybe 
you could restrict these to *ADD also, with an initial program to add the 
user when signed on. Other issues here - like removing when interactive 
session ends.

HTH

Vern

At 04:29 PM 3/18/2003 -0500, you wrote:
> Will I run into any problems with that ? I had thought about that but wasn't
> sure...
>
> Chuck
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Paul Nelson
> Sent: Tuesday, March 18, 2003 4:23 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: Restricting Nosey Users Message Access
>
> Have you tried restricting the message queues?
>
> Paul Nelson
> Arbor Solutions, Inc.
> 708-670-6978 Cell
> 708-923-7354 Home
> pnelson@xxxxxxxxxx
>
> ----- Original Message -----
> From: "Chuck Lewis" <clewis@xxxxxxxxxx>
> To: "midrange-l" <midrange-l@xxxxxxxxxxxx>
> Sent: Tuesday, March 18, 2003 2:59 PM
> 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