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,
Post an idea
Upvote ideas that matter most to you
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.
needs a solution for deadlock between multiple change streams
Please refer to the PMR 10350,69G,760 ---------------------------------------- Customer would like to avoid a deadlock situations between multiple change streams when he started some subscriptions in test scenario of source server failure. Since IIDR for IMS could not detect this deadlock situations, customer must check a deadlock situation manually and need a recovery operation when problem occur. He needs a short term and long term solutions. The sort team solution is to detect the deadlock situation and to report a failure. The long term solution is to resolve the kind of contention issue. . The problem sequence in this PMR is as follows. 1. simulated source server failure (CANCEL SOURCE-SERVER) 2. target server detected the source server failure. 3. restarted the source and target server 4. START,REPL 5. S2 secondary change stream was accessing and holding a SLDS dataset(A) in the VTS tape. 6. S3 secondary change stream was waiting to access a SLDS dataset(A) in the VTS tape. 7. S3 secondary change stream was accessing and holding a SLDS dataset(B) in the VTS tape. 8. S2 secondary change stream was waiting to access a SLDS dataset(B) in the VTS tape. . If these archive log datasets are on on DASD, they can be accessed concurrently by multiple change streams. so deadlock does not occur.
Do not place IBM confidential, company confidential, or personal information into any field.