Re: Security

*USE at the library level will let a user pretty much do anything to an object 
in
that library that is not excluded by authority on that object.  One exception
I'vce found is the ability to add a member to a file, which requires *CHANGE at
the library level.

*USE on the object level only lets a user read data in a file - not change it.
Note that they could download the file to a PC (but couldn't upload & overlay).
So take this example:
Library authority *USE
FILE1  - *PUBLIC *USE   <- USER1 can read file
FILE2 - *PUBLIC *ALL <- USER1 can change data in file, but not add a member
FILE3 - *PUBLIC *ALL, USER1 *EXCLUDE <- USER1 cannot access file

mgraziano@badgermeter.com wrote:

>      Question:
>                 If a library has security for a user of *use
>                 will this user be able to update files in the library and
>                 If files were created with public *use.
>
>                 Or is the security level at the library used for all
>                 objects under it.
>      My understanding is that the Library *use means the user can use all
>      objects under it and that the security of the files (objects) is used
>      to check what the user can do to the file.
>
> +---
> | 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 MIDRANGE-L-UNSUB@midrange.com.
> | 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 MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---