Re: ODBC Security

["alan shore" <SHOREA@xxxxxxxx>]

Firts of all, let me admit that I have to become more conversant with ODBC, 
but, anyway, here goes.
Why is *PUBLIC authority *CHANGE, and not what it should be *EXCLUDE. Grant the 
users, either individually or by GROUP PROFILE, *CHANGE authority. Then whether 
from the AS/400 or for ODBC, they should be able to access the database, 
surely. 

>>> Quazy <quazy@SoftHome.net> 11/09 12:25 PM >>>
How does everyone deal with security on the 400 and the ability to use ODBC?

If production files are set to public authority to *change, what can I 
do.  users don't have access to manipulate the data from the AS/400 (I have 
taken all those ways away).  But even if a user with basically no authority 
gets on through ODBC they could do anything they want to the database.


What is there you can do?

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

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