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 Under review
Workspace Db2 for z/OS
Created by Guest
Created on Dec 10, 2021

Increase commits in STOSPACE

We opened a case: Contentions on SYSINDEXES during STOSPACE.

The stospace on a large stogroup causes many timeouts and deadlocks on the SYSINDEXES to a JDBC application which is the most used in our center.

The answer in the case is the following:

"STOSPACE is an utility that scans and updates the catalog heavily. STOSPACE commits only a few times after updating all tablepart and indexpart entries, and then all stogroup entries. Regarding your question about contentions with dynamic threads - like for a simple select on a user table that is getting a TIMEOUT (SQLCODE -913 / rsn00C9008E) during STOSPACE run:STOSPACE is updating SYSINDEXES (TS SYSTSIXS) and holds an exclusive LOCK. During that time readers are blocked. When a statement (like the SQL SELECT in your case) is prepared, the Optimizer is accessing CATALOG TBs like SYSINDEXES, and this could lead to contentions (DSNT376I).

Is it possible to increase the commit frequency of the Stospace?

Otherwise we cannot perform the stospace because it is a 24x7 application

Needed By Quarter