Re: QPWFSERVER

Eric,

It's my understanding that QPWFSERVER only prevents users from viewing libraries
in the Network neighborhood.... effectively blocking only the SQL 'List'
function.  It does not actually secure the libraries or the resources in them.
To do that you need to either implement object level security (if you can), or
use exit programs to block actions that you don't want to happen.

The QPWFSERVER authorization list doesn't really 'secure' anything, it just 
makes
it harder for users to see what they can get at.

jte




Eric wrote:

> I've *EXCLUDED *PUBLIC from the QPWFSERVER authority list in order to
> temporarily prevent access to QSYS from C/A Operations Navigator and
> Network Neighborhood.  It was my understanding (from a previous COMMON
> session) that this would in effect "close the door" to the QSYS library
> tree.  It isn't working.  Does anyone know why?  Thanks in advance.
>
> Eric Kempter
> Director of MIS
> Commair Mechanical Services
>
> +---
> | 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
> +---



--
John Earl
PowerTech Toolworks
johne@toolnet.com
253-858-7388

Riley Nichole Earl, Born 7/6/98 - 8lb 11oz.  Already an AS/400 fan!
--


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