RE: Giving users "deposit" access to an output queue.

It may not be ideal but, you could always use the spooled file apis to
create your own "WRKSPLF". Since you do the programming you can control
who gets to do what. I seem to rremember someone put together something
like what you would need many years ago for News/400 but it could have
been Midgrange magazine also.



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, March 26, 2008 12:42 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Giving users "deposit" access to an output queue.


I want users to be able to put any spool file into a particular output
queue. However, once it is there, they cannot delete it, etc. They're
interfering with FAX/400.

I tried creating the output queue with AUTCHK(*DTAAUT) and making
*PUBLIC
*USE however they could still delete the spool file. If I make it
*EXCLUDE they cannot deposit. So I left it *EXCLUDE and they could do a

SBMJOB and that process (running under a different profile) would then
put
it into that output queue. However, they could still delete the spool
file while it was in that output queue.

I have "Display any file" set to *NO.

With this authority they cannot display or delete other spool files on
that output queue, however they can still abuse their own and I'd like
to
stop that.


Rob Berendt