Re: Securing output queues

["Henrik Krebs" <hkrebs@xxxxxxxxx>]

I must admit, that my first reaction was: Do they really care about
security in a shop with several ordinary users having *ALLOBJ. The days
of menu-security are way past in theese networking days.

Question: Do those users have CA/400-access to 'QSYS.LIB/....'?

Goodbar, Loyd (AFS-Water Valley) wrote:

> We have some output queues we wish to secure. The problem is several
users
> have *SPLCTL and *ALLOBJ. We want to secure an outq such that only
specific
> users can view/change spool files in that queue. I've created an outq
with
> public *EXCLUDE, and added an authorizaton list to it. I've revoked my
> ownership of the queue to QSECOFR. Even if my name is not on the
> authorization list, I can still view and change spool files in this out
> queue. My profile has *ALLOBJ and *SPLCTL, among others. What are my
> options?

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---