Re: Restricting User Access

Well, assuming your level 30 (the most common lebel), then any new user
profile will access at *PUBLIC authority (until you give it or its group
profile(s) private authorities(unless of course, it has *ALLOBJ)).  

So first, you'd have to RVKOBJAUT for *PUBLIC for all objects (or at
least all libraries - probably a better plan to make sure all libraries
are secure, but then have all objects within a library have *PUBLIC *ALL
authority).  Then no one without explicit authority or *ALLOBJ authority
will be able to get at anything.  



Chris Ring wrote:
> 
> Hello everyone!
> 
> I have a security question that some of you may be able to help me with.
> 
> Simply put -- Do you know if there is a way to create a user profile that
> is NOT authorized to anything?
> 
> I'm trying to set up a user ID on the '400 that basically is not authorized
> to anything.  I would like to then set up specific objects (pgms) that the
> user is authorized to.
> 
> Any help is greatly appreciated .....Thanks!
> 
> Chris Ring
> Senior Systems Analyst
> Arksys Inc.
> Little Rock, Arkansas
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
> | To unsubscribe from this list send email to MAJORDOMO@midrange.com
> |    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---