Skip to Main Content

This is an IBM Automation portal for Integration products. 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Dec 14, 2023

Add command or automation to reduce CURFSIZE immediately

Use case:

RDQM with limited space. One Xmit queue used all space as partner queue manager had issue. Once issue was solved, draining Xmit queue is slow.

It would be beneficial to release q file space immediately once messages were consumed, say after 20% reduction, even queue is still in use by channel.

According manual there are only 3 possibilities when space is released:

Note: When a queue has messages removed from it, the CURFSIZE attribute might not decrease immediately.

Typically, unused space in a queue file is only released in the following circumstances:

-When no applications have the queue open

-After 1000 writes to the queue manager log, or

-At queue manager shutdown

Please add a 4th possibility:

Implement a command to enforce release of unused space.


Implement an automation which reduces space automatically once 20% is unused.

Idea priority High
  • Admin
    Mark Taylor
    Feb 20, 2024

    A queue manager already looks for opportunities to decrease queue file sizes on disk during checkpoints as highlighted by the submitter, by default a checkpoint occurs every 30 minutes or every 50K checkpointable operations (puts/gets/commits/etc) but that can be tuned up or down.

    There would be limited value to provide a further command to request this, which could be always denied if the queue is still open and in use by applications or channels.

    Capacity planning for a queue manager should ensure that enough disk space is provided to cater for queues filling and so it would not be recommended to provide under-provisioned storage for a queue manager. Queues (and the disk footprint) are intended to grow to meet demand and MQ is designed to expect that resources needed to handle such spikes are likely to be needed again.