I am assuming that you want to allow your users to be able to view the data, just not change or create something new. If that's the case, users with *USE authority to the file will be able to view, but not modify the data (that requires *UPDATE authority, which is included in *CHANGE.) To add records requires *ADD authority, which is also included in *CHANGE. Using object level security within OS/400 will ensure that users can view and not update or add records from any interface, not just with SQL.
If you don't want to put object level security on the file itself, you MAY be able to accomplish your objective by writing or buying an exit program and authorizing users to only certain sub-functions of the SQL server. However, using OS/400 object level security on the file itself is the most secure method.
================================== MORE INFORMATION ON THIS TOPIC ==================================
The Best Web Links: Tips, tutorials and more.
Search400's targeted search engine: Get relevant information on security.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Read this Search400 Featured Topic: Secure your iSeries
This was first published in May 2002