RE: ODBC Connections -- MIDRANGE-L

Subject: RE: ODBC Connections
From: "Chris Bipes" <chris.bipes@xxxxxxxxxxxxxxx>
Date: Tue, 2 Dec 2008 10:34:05 -0800
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I find the easiest way is to create a library with read only views to
the files / fields you want others to have access to. Exclude everyone
from direct access to the physical files. Then grant the appropriate
authority to the views. No special programming or user authority file
to maintain. This uses the iSeries native security.

Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----

Wintermute, Sharon wrote:

I need to secure the ODBC connections to be read only. I am looking

the Exit points and trying to figure this out. Can someone guide me?

As an Amazon Associate we earn from qualifying purchases.

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.