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 Future consideration
Workspace Optim
Created by Guest
Created on Oct 22, 2021

Same level of performance in extract processes in DB2 and IMS when qualifing the column of the cluster index

Since OPTIM V11.7, we experienced dramatic performance regressions with the component "Extract on an IMS Database".

The extract criterion is almost all the fields of the primary/cluster key.

The database contains 15.6 millions records - 1 hit is expected

With V11.3, the research consume 0.1s CPU records and read few records

With V11.7, the research consume 60s CPU, 15 mn elapse an read all the database

The pseudo SQL is :

SQL //CODFAM = 'A' AND ETAB = '000' AND CODDEV = ' ' //

// AND NCPTP > '00021107107' //

The support aknowleged the facts but answered that the solution required too huge work to optimize the SSA'qualification SSA and the Selection/SQL criteria

We will be very pleased if you accepted to review the 11.7 code so that we will have equivalent performances in IMS and in DB2 when using cluster index

Needed By Month