Re: Limiting ODBC connections for a user

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Gary

I'm going from memory - I thought ODBC/JDBC used the QZDA* exit points. 
Are you just saying that they ALSO use the SQL exit points?

Vern

On 7/31/2012 5:36 PM, Monnier, Gary wrote:
> You can use an exit program on the SQL exit point.  ODBC and JDBC use the same exit poing.  If you don't want to write your own there are several packages available.
>
> Gary Monnier
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mike Cunningham
> Sent: Tuesday, July 31, 2012 11:42 AM
> To: Midrange Systems Technical Discussion
> Subject: Limiting ODBC connections for a user
>
> We have a system running on a linux box making ODBC connections to the iSeries to get DB2 data. At times that system gets used heavily and we see 50-60 ODBC jobs at one time using CPU time. They all connect as the same user over ODBC. Is there a way to limit the number of jobs that QZDASOINIT will start for a particular user?  We have other jobs, including native java apps that also use QZDASOINIT but as a different user. The java connections never cause problems and we don't want to limit those.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.