This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
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.
IBM Employees should enter Ideas at https://ideas.ibm.com
See this idea on ideas.ibm.com
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 |
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.
Dear Ermanno,
Thank you for submitting this enhancement request.
The Db2 for z/OS development team has reviewed it and believes that the information gathered and made available by the STOSPACE utility is already available through real time statistics and other catalog data. That said, they may aim to improve commit frequency for those who choose to use STOSPACE.
The idea has been moved to 'Future consideration'.
Sincerely,
The Db2 for z/OS Team