RE: ODBC Connections -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

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

Subject: RE: ODBC Connections
From: "John Earl" <john.earl@xxxxxxxxxxxxx>
Date: Wed, 3 Dec 2008 10:06:15 -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>

There is an utility called ODBCLOG, by Bob Pascas. It comes

This doesn't do read only - it only monitor's the ODBC connection exit
point (QIBM_QZDA_INIT) and not any of te ODBC data transfer exits (the
most important of which is QIBM_QZDA_SQL2).

As a handy way to regulate _which_ users can use ODBC, it looks like it
would wortk, but it does not log or regulate content transfer once a
users has been allowed to use ODBC.

jte

--
John Earl
The PowerTech Group, Inc.
Direct: 253-479-1408
Mobile: 206-669-3336

www.powertech.com

As an Amazon Associate we earn from qualifying purchases.

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.