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 updateson 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
Rotate an archive-enabled PBR tablespace without causing a deadlock
When we try to rotate partitions of an archive-enabled PBR tablespace, Db2 requires us to disable archiving before the rotate then re-enable archiving after the rotate. However, when we re-enable archiving we cause a deadlock with CICS and the online transaction fails. In order to prevent the deadlock we have stopped rotating partitions and are just adding a new partition at the end of each month and emptying out the oldest one. Since we cannot drop the old partition we will end up with many empty datasets from the partitions that we should have been able to rotate out. Possible solutions are: 1) allow us to rotate partitions without having to disable archiving, 2) Allow us to drop the old partition after adding a new one, 3) Allow us to force the CICS transaction to survive the deadlock resolution (least desirable option because we still have the problem, we've just created a workaround).
Do not place IBM confidential, company confidential, or personal information into any field.