Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Feb 3, 2020

force the execution of a query on an accelerator if more than one is available.

The CURRENT ACCELERATOR special register specifies a preferred target accelerator or accelerators to which Db2 sends dynamic SQL queries.
But If you have multiple accelerators on which the same set of Db2 tables are accelerated, by default the workload balancing algorithm (WLB) distributes the queries based on the queue length on each accelerator. When the CURRENT ACCELERATOR special register names a particular eligible accelerator server, Db2 considers sending eligible SQL to that server before it sends it to other accelerator servers. But If the accelerator server that is named by the CURRENT ACCELERATOR isn't available, Db2 considers other available accelerator servers.

MY REQUEST: Create  new special register, for sample: CURRENT FORCE ACCELERATOR, that forces the execution on a chosen accelerator. And If the accelerator server that is named by the CURRENT FORCE ACCELERATOR  isn't available then the query run on DB2 or fail if CURRENT QUERY ACCELERATION is set to ALL.

  • Guest
    Apr 8, 2020

    Hi Dennis,

    Thanks you for your review of my idea.
    Thanks for your time and your help.


  • Admin
    Dennis Lukas Mayer
    Apr 8, 2020

    It is currently not planned to add a new special register to force a query to an Accelerator but this workaround might help:






    SELECT <your query> FROM <yourtable>, ACCELERATORS.ACC1 for fetch only