× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.