Re: Controlling ODBC access -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Controlling ODBC access
From: Luis Rodriguez <luisro58@xxxxxxxxx>
Date: Wed, 7 Aug 2019 09:24:45 -0400
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Brian,

Many years ago we implemented (in V5R3) some routines called ODBCLOG, by
Bob Pascas (maybe Google it?). Basically, they used SQL's exit points to
register in a table the user's accesses. We extended them in order to check
the user's SQL command against a list of allowed commands (based on the
user's permissions).

A quick search gave me the exit point as QIBM_QZDA_SQL2. That surely must
have been changed (V5R3 was a long, long time ago).

HTH,

Luis

Luis Rodriguez

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Controlling ODBC access , Luis Rodriguez

This mailing list archive is Copyright 1997-2026 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.