RE: QPRINT authorities

Terry:

Three additional items to consider...

1. *SPLCTL for your SysOpr

With this special authority granted to your SysOpr, a lockout shouldn't be a 
problem. Given OPRCTL(*NO) and DSPDTA(*OWNER), your various *JOBCTL users 
shouldn't be as much of an issue and your *SPLCTL user(s) shouldn't be affected.

2. AUTCHK(*OWNER)

This additional *outq attribute might be useful as well.

3. QAUDLVL *SPLFDTA and *PRTDTA and job accounting

Auditing of printing and spooled file actions may be useful. Also, job 
accounting journal entries related to printing can help especially when a 
report has disappeared from the system because it was printed rather than 
deleted. Though these don't directly interfere with user actions, they can sure 
help determine "What happened to my report?!" -- always nice to answer "You 
printed it on printer PRT01 at 10:00 this morning."

Tom Liotta

midrange-l-request@xxxxxxxxxxxx wrote:

>   7. QPRINT authorities (terryf)
>
>    We have a system running V4R5 on which the base app we run gives all users
>*JOBCTL spec authority.  All users use QPRINT as their default printer, and
>dump a good bit there for retrieval via OPSNAV.  I am dealing with users
>going in thru WRKOUTQ to the QPRINT que and reading, deleting, or whatever,
>other users spool files. 
>
>    It is my understanding that setting the DSPDTA to "owner" and OPR to "no"
>for the QPRINT que will prevent this, however I am not clear about how to
>keep the sysopr, who logs on under her own name, from being locked out as well.

-- 
-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertechgroup.com


__________________________________________________________________
Try AOL and get 1045 hours FREE for 45 days!
http://free.aol.com/tryaolfree/index.adp?375380

Get AOL Instant Messenger 5.1 for FREE! Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promos=380455