What it means
The queue has not reached its maximum depth, but the storage behind it is full, so the message cannot be written. The code can also appear in a report message from a channel. IBM states this reason does not occur on z/OS.
Typical causes
- The file system holding the queue manager's data is full.
- A runaway program is filling queues faster than they are emptied.
- Large messages or deep queues have grown over time without monitoring.
- Other files, such as traces or dumps, filled the same file system.
How to fix it
- Check free space on the queue manager's data file system.
- Look for a program in a loop, and stop it if needed.
- Clear old traces and error files, or add space to the file system.
- Find the deepest queues and fix their consumers.
Example
Illustrative only; names and values are invented.
MQPUT failed CompCode=2 Reason=2056 Queue=APP.LOG.QUEUE
df -h /var/mqm