Re: OUTQ Security

["Jim Franz" <franz400@xxxxxxxxxxxx>]

from a previous answer in '99

The splctl is part of your problem. Were the outqs created w/default
parameters? There are a couple variations on the parms. To have an outq
where only the user/group that created a report can see its content, try
CRTOUTQ outq(xxx) dspdta(*owner) oprctl(*yes) autchk(*owner) aut(*use).
Users w/ *jobctl can manage the queue, but not see inside the reports.
Remove operator control with oprctl = *no. Could also change aut =
*exclude.  User w/ *allobj can only view their own spool files in a
queue w/ dspdta = *owner. The  exception is *splctl. It overrides all
outq parameters. Only Qsecofr needs this. See the book from Duke Press
'Implementing AS/400 Security' by Wayne Madden & Carol Woodbury. They
have a detailed explanation.
jim franz

----- Original Message -----

From: KirkG@PacInfoSys.com

To: midrange-l@midrange.com

Sent: Thursday, July 26, 2001 7:27 PM

Subject: OUTQ Security

I have a client that somewhere in the past has given the majority of the users *SPLCTL authority so they can control there own outqs/writers etc. Now they have a new app that they want to secure the output to only 6 or so users. From what I can read *SPLCTL trumps most if not all security placed on the outq.

The 1st step appears to remove *SPLCTL and to change *PUBLIC to *EXCLUDE but then what is the best way to allow users to control selected outqs?

Grant each user specific authority to the outq, AuthorityList?  ??

---------------------------------
Kirk Goins
IBM Certified AS/400 Technical Solutions
DataMirror High Availability Certified
Pacific Information Systems - An IBM Premier Business Partner
503-674-2985             kirkg@pacinfosys.com
"WE KNOW TECHNOLOGY"
---------------------------------