Re: ODBC Connections

[Luis Rodriguez <luis.rodriguez2@xxxxxxxxx>]

John,

Concur with the fact that Bob Pascas' utility is for monitoring only. That being said, I thought that the OP needed some starting point in order to monitor its ODBC connections.

In fact, some time ago I used ODBCLOG's source code and the exit point you mentioned (QIBM_QZDA_SQL2) as the basis for a program that analyzed the incoming SQL statement(s) and checked the user's authorization to certain keywords to be found there (UPDATE, INSERT, etc). Sort of poor man SQL exit point manager.

Regards,

Luis Rodriguez

IBM Certified Systems Expert
eServer i5 iSeries Technical Solutions


--- On Wed, 12/3/08, midrange-l-request@xxxxxxxxxxxx <midrange-l-request@xxxxxxxxxxxx> wrote:

RE: ODBC Connections
Wednesday, December 3, 2008 2:06 PM
From: "John Earl" <>
To: "Midrange Systems Technical Discussion" <>
> > 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