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

Don,

At 04:00 PM 6/18/97 -0400, you wrote:

>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....

Post V3R1?  I would create separate "printing group" profiles for each
logical group of users and add the printing groups to the user profiles as
supplemental groups.  Prior to V3R1 you'll have to authorize individuals to
queues individually.

Then change the authority of the outq's and print devices so that *PUBLIC
was *EXCLUDE and the printing group (or the individuals) has *CHANGE
authority over the printer device and the output queue.

Next if many people have *JOBCTL special authority in their user profile,
you'll want to change the outq description (WRKOUTQD, then F13) so that it
is OPRCTL(*NO).  When it's *YES anyone with *JOBCTL can work with queue
entries regardless of their object authority to the queue.

While you're in the CHGOUTQD screen, you may want to change the Authority to
Check (AUTCHK) parameter to *DTAAUT.  This allows anyone with *CHANGE
authority on the queue to manipulate entries on the queue (I think this is
what you want).

Finally, be aware that anyone with *SPLCTL can do whatever they wan to the
queue ( I think you knew that :), so limit that special authority.

HTH,


jte



*************************************************
* John Earl     Gig Harbor, Washington  U.S.    *
* Email:        johnearl@blarg.net              *
*************************************************

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *