Vern,
It may have changed in 6.1 or 7.1 but generally yes ODBC and JDBC connections go through QZDASOINIT jobs. At least one vendor uses, or did, their own exit point. The parameter list is/was an expanded version of the DDM exit point parameter list.
Exit points for ODBC/JDBC....
QIBM_QRQ_SQL format RSQL0100 - Original Remote SQL Server
QIBM_QZDA_SQL1 format ZDAQ0100 - Database Server - SQL access
QIBM_QZDA_SQL2 format ZDAQ0200 - Database Server - SQL access (I suggest an exit program on this one over _SQL1)
And, as I said, some vendors have their own exit points you can cover. Showcase is one vendor that at least used to provide its own exit point.
There is also the DDM/DRDA connection you can cover. At one point in the past Showcase utilized the DDM/DRDA interface rather than their own exit point. Other vendors also utilize the DDM/DRDA interface.
The QIBM_QSQ_CLI_CONNECT exit point may not directly provide a method to accept or reject a user but you can send an escape message to the exit program's invoking program or to the job.
I know a number of admins are not all that impressed with exit point programs but a great deal can be done with exit points (auditing, securing, information gathering, etc.).
At least one vendor I know of provided you a way to extend their product by invoking your own exit program(s) from theirs. The nice thing about the product was adding and removing you own exit program(s) did not require ending servers. You just changed a configuration setting. In fact, you didn't even need to utilize their product beyond being registered to the exit point if you didn't want to. Wonderful for using change control software to install your own changes to exit programs.
The EDRSQL (extended dynamic remote SQL) server didn't go through QZDASOINIT or have exit points as of V5R4. I haven't looked at V6.R1 or above to see if this has changed.
Gary
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: Wednesday, August 01, 2012 7:18 AM
To: Midrange Systems Technical Discussion
Subject: Re: Limiting ODBC connections for a user
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.
--
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.
midrange.com
