MQRC 2056: Queue storage unavailable

What it means

MQPUT or MQPUT1 could not obtain storage space for the queue. This is a storage-capacity problem rather than simply reaching the queue's configured maximum message count.

IBM states that this reason does not occur on z/OS. A z/OS storage incident needs its actual platform-specific return code and messages, rather than a distributed queue-file procedure.

A troubleshooting example

A downstream service stops overnight while the producer continues at its usual rate. Disk allocation is exhausted before the team's queue-depth alert fires, and puts return 2056. Inspect both capacity and flow rates, then agree how the backlog will be processed after service returns. Validate that storage remains stable during catch-up. A useful follow-up is an alert on the time remaining at the observed growth rate, alongside ordinary depth thresholds, so the next outage is caught before storage is exhausted.

Common causes

• The filesystem or underlying storage supporting the queue has no usable space.
• A producer loops unexpectedly and adds messages much faster than consumers remove them.
• A consumer outage allows normal production to exhaust the available storage allocation.

How to find the problem

1. Capture the affected queue manager, queue and put timestamp. Read queue-manager and operating-system storage messages together.
2. Check free space, allocation limits and the relevant storage mount. Confirm that the application is examining the filesystem actually used by that queue manager.
3. Compare queue-depth and put/get trends with their normal baseline. Identify a stalled consumer or sudden producer-rate change.
4. Distinguish this failure from reason 2053, which concerns queue fullness, and from a logging failure that affects a unit of work.

How to fix it

• Stop uncontrolled growth and restore approved storage capacity. Ask the MQ and storage administrators to choose the recovery method.
• Restore the intended consumer or correct a producer loop. Merely adding space does not resolve continuing unbounded message growth.
• Do not delete queue-manager files or discard business messages as an improvised cleanup. Recover through supported administration and the application's retention and replay procedures.

What it looks like

Illustrative diagnostic notes; not an IBM message template.
MQPUT Reason=2056
Check queue-manager storage mount and free space.
Compare producer rate, consumer rate and backlog growth.
Do not remove queue files manually.

Technical reviewer: Albert Joseph, WND Software.

Updated 2026-10-23. IBM documentation checked for this article. Written in our own words. For the full reference, check IBM’s MQ documentation for your version.