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 Not under consideration
Created by Guest
Created on Mar 7, 2018

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
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.

  • Admin
    Eric Su
    May 21, 2021

    [IBM Update]


    Thank you for filing this requirement and for your interest in keeping our IMS/VSAM Data Replication technologies vital and successful. We depend on your continued interest and ideas to help ensure our products keep pace with market needs and industry standards.

    Although we do agree that your request is valid, after monitoring your request for more customer demand over the last few years and applying other relevant evaluation criteria, unfortunately we won't be able to accept your request at this time. However, if there is still an important business need, we encourage you to file a new idea accompanied with any additional information that could help us prioritize the requirement in the future.