Managing Users that Manage their own OUTQ's....

[Don <dr2@xxxxxxxxxxxxxxxx>]

Oh great guru's who manage multiple sites, printers at various locations
and other ilk that goeth bump in the night....we have a problem and need
some sage words of wisdom  (and no, I'm actually rather sober at the
time...)

We have a situate where a company has multiple printers, at multiple
locations, with multiple users that are attempting to manage the printing
resources sans system operators for each printer/location.  The problems
start with having them do a WRKOUTQ and seeing ALL the OUTQ's, when we
only want them to see theirs....and also having to add SPLCTL as a SPCAUT
to their USRPRF...which I'm not sure we want to do as a final solution.

How can we only allow a user to see THEIR list of OUTQ's and and only
WRKWTR functions of the writers that are specifically assigned to them.
AND, I don't want them to be able to see/view/manipulate someone's
SPLF's...and I don't want to create a scenerio when I'm making more
secadmin concerns for my sysopr than they have time for...which right now
isn't a whole heckuva whole lot....

Many thanks!

Don in DC....

"Reality, what a concept...."

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *