IBM Power Ideas Portal


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Add a new idea Subscribe
Status Submitted
Workspace IBM i
Categories IBM i Access Family
Created by Guest
Created on Jan 6, 2026

RELATED IDEAS

IBM i Access ODBC driver query execution timeout

My organization is using PHP/Laravel and the IBM i access odbc driver to connect to DB2.

We have had a few scenarios where the php application sends a sql query and then waits indefinitely for the result, until PHP's max execution time kicks and kills the script. (See additional details).

I do understand that a predictive query governor exists. It makes a lot of sense, but I do not believe it would've helped in the previously described scenarios because under normal circumstances all of my queries are quite fast.

So in addition to a predictive query timeout, an actual run time timeout still has value. I do not think these concepts are mutually exclusive they could be used together. The predictive timeout can reject expensive queries before they even start and the actual runtime timeout can kill queries that are running longer than expected (there's probably an issue).

I am also aware of SQL cancel. However that is not trivial to implement. For every query my application issues I will need two threads - one to issue the query and another to time the former/issue sql cancel if necessary. That is a lot of development overhead - a simple configuration value would be much easier.

Idea priority Low
  • Guest
    Jan 7, 2026

    I think this is already implemented with the use of the Query Supervisor: https://www.ibm.com/docs/en/i/7.6.0?topic=tools-query-supervisor

    Reply

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.