Re: Spool File lock down

Any particular reason why the user has 'User class = *SYSOPR' and 'Special
authority = *JOBCTL'?
That seems pretty powerful for a "user"
If it was me I would make ALL "users" just be that - *USER, with NO special
authority
Just my two pennorth



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill



midrange-l-bounces@xxxxxxxxxxxx wrote on 04/30/2007 01:57:41 PM:

We have a need to lock down a user so he cannot delete a spool file
for printer (Q6). The CL that runs does an override to that printer.
We do not mind him looking at the prints but not being able to
delete them. Other users have access to that printer and we do not
wan to affect them.
The user has 'User class = *SYSOPR' and 'Special authority = *JOBCTL'.
Any help/ideals on the best way to do this would be appreciated.
William Moore


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.