Re: QSYSOPR message queue

Pete Hall wrote:

> At 03:58 05/22/2000 , John Earl wrote:
> >A user needs *opr and *add to place messages on the queue, and *opr, *read &
> >*add  (rather than *upd) to answer messages.  It turns out that when you
> >answer a
> >message you are actually adding a new message to the queue that answers
> >the old
> >message (that's why we see inquiry messages show up twice in the
> >queue).  You're
> >not actually (or directly?) changing the old message.  Weird, but that is
> >the way
> >it is.
>
> Ok. What's the magic combo then, that will allow *public to put messages on
> the queue, but not allow *public to answer them? I know I got this to work
> once. I'm just not sure exactly what the solution was. Granted you need add
> data authority to add a reply message, but don't you also need update?

It's kind of screwy, but all you need is *add authority.

However, if a user has *add authority, doesn't have *read authority, then it
becomes "practically" very difficult for them *add a reply to an existing
message.  Screwy, yes.  But that's the way it appears to work.

> Replying does modify the original message status, does it not? I'm really
> not sure. I wish I could test it, but alas, I don't have the authority...

I just don't know, so I won't hazard a guess.

jte


--
John Earl                               johnearl@400security.com
The PowerTech Group                     206-575-0711
PowerLock Network Security              www.400security.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
+---