× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. February 2007

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.