This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
DBOpen Exit Point takes care of ANY database access, regardless what type. This results in performance problems.
Severals performance tests show that from 100% DBOpen Acess apx. 95%-99% are coming from Native I/Os. This is from exit point technology prospective less important because all this are running in native environment, not connected to any external device.
To avoid performance problems when registering an exit program we request to add beside of existing exit point format QIBM_QDM_OPEN DBOP0100 a new Format DBOP0200 that skips on operating system level all native I/Os (NTVIO) and call the exit point only for all others (OPNQRYF, Query/API, Other Non-SQL, Interactive SQL, ODBC, Other SQL, QSQPRCED API (SAP) and SQL CLI).
For clients that are interested only in ODBC transactions, optional another Format DBOP0300 may call the exit point only in case of ODBC connections (Job names QSQSRVR, QZDASOINIT, QZDASSINIT,...)
This ideas was already discussed with Scott Forstie but not yet decided.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Db2 for i development team
IBM Power Systems Development
Not quite true - the exit point program is called ONLY on FULL open of a database table, not for ANY database access. So the program is not called after the job has opened the table.
The exit point offers user handling of table opens - allowing additional checks besides object security and rejecting the open under some circumstances.
The exit point program is called from ANY interface. If you do not want native opens, check for this as your frst step in your exit program and return immediately. The performance penalty for this would be absolute minor.
If you have 95%-99% native table opens, you should have a look at the number of full opens performed in your application, e.g. using the SQL Performance Center, which shows this on the first page. Opening a table is a heavy operation and should be reduced as much as possible.
Best regards,
Christian
CEAC member and IBM Champion