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
Workspace Db2
Created by Guest
Created on Oct 4, 2016

Allow complete acces path in optimization hint (like db2 for ZOS)

We have the same cobol application that on both z/os and luw.
We are using static sql in packages. We run 12 schemas using the same sets of tables in each for manual application parallelism.
Occasionally a package for a given schema will flip access paths when bound/rebound and in the case for which I raised this pmr, it took hours instead of seconds.
For LUW there are only a limited number of things we can do - reopt once, hacking stats etc, none of which is ideal or always solve the problem.
For db2 for Z/os we can take an access path previously used from the plan table (or one currently being used in a defferent schema) and use this to tell the optimizer what to do (we have been doing this for 10 years and it so far has always solved the problem).
We do not have this facility for LUW which causes us problems.
What I would like to be able to do is generate the complete access path in xml format and be able to use this as input as an optimization guideline. At the moment you can only pass very limited guidelines which are not much use for complex sql statements - which mimics the funtionality of Oracle but not DB2 for zos.