Dynamically increasing Short message Queues

Hi Solomon,
Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.
When choosing new features to add from the list of requirements in our backlog, we assess which will bring the most value to as many clients as possible and prioritize those.

At this time, after reviewing this request for enhancement and assessing its potential value, we have decided to reject it. We think it’s a great idea but we are rejecting RFE 81727 because we don’t feel we can deliver it within the next 18-24 months which is the goal we have set for RFE deliverables as part of our IMS Gold program.. You are welcome to resubmit this RFE at a later date and we will reconsider.

We appreciate your input to IMS, and we hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of IMS.

Thank you.
Sincerely,
Deepak Kohli - deepakk@us.ibm.com

I am not being the customer but still interested in this RFE, my answers are as follows:
1. We haven't opened an RFE as this has occurred in our test environment and we are aware of the need to cold start. However, it would be useful to be able to, after the afflicted application gets stopped, expand the message queue without throwing away data.

2. We have run out of long message queue more than short, so a solution to both would be preferred.

3. We are considering IMS Shared queues, but are holding off until we get funding for a tool to monitor and modify those queues.

4. Unfortunately, no, but we are investigating it, and have generally been able to identify the offending application by browsing the queue after IMS crashed.

Yes, this is part of the solution, where we also need a tool for managing it as a second part of the solution.

We are looking into this RFE and we have the following questions:

1. Was there a specific incident that led to the creation fo this RFE? If so, please let us know the details (and the PMR number if there was one), so that we can better understand the background.

2. The RFE specifically asks about increasing the short message queue capacity. IMS queue manager has both short and long message records; is there a reason this is specific only to short messages?

3. Do you use or have you considered using IMS Shared Queues? With shared queues, the IMS queue manager can dynamically expand and compress the internal queue manager buffer pool. Also, the shared queues structure size can be dynamically altered to add additional capacity, without requiring an outage.

4. If you are not using Shared Queues, do you use any sort of tool to monitor your queue usage and prevent queue full conditions?

Thank you!