RE: Read-Only ODBC Access

In our (Centerfield) exit point security solution we call this concept
proxy-user.  It works fine for number of our customers so I don't see
anything wrong with your approach.

Elvis

Celebrating 10-Years of SQL Performance Excellence

-----Original Message-----
Subject: Read-Only ODBC Access

We've been investigating giving some of our users read only access to 
our iSeries data using the iSeries Access ODBC driver.

I know you can set the driver to be read-only, but we're not happy with 
how easy that is for the user to change. I believe the nature of our 
bespoke ERP package means that setting file permissions based on user 
name is not workable. So we're really left with the ODBC exit points. I 
have be in touch with Powertech, and got a quote for their Network 
Security product. However, another suggestion has been made:

Write our own exit point program, which will allow ODBC access to one 
user only (say ODBCUSER). Then set file permissions for just that user.

Apart from all the other exit points going unmonitored (which is no 
worse than we are currently) can any flaws be suggested with this logic? 
Would I be able to set most files so that ODBCUSER would be unable to 
even see them, and relevant files that we decide to make available via 
ODBC to read-only? How do I do this?

Thanks

Guy