What it means
The queue manager found the object's definition inconsistent or unreadable, in memory or on disk. The object can be deleted, though some of its storage may not be freed. On z/OS shared queues, it happens when the queue's coupling facility list header details have been reset, for example after DELETE CFSTRUCT.
Typical causes
- Disk or file problems damaged the queue manager's object files on distributed platforms.
- A failure left the in-memory and stored definitions out of step.
- On z/OS, the CF structure used by a shared queue was deleted.
- Recovery data is not available because the queue manager uses circular logging.
How to fix it
- On AIX, Linux and IBM i, read the FFST or FDC files for details.
- With linear logging, try to recover the object from its media image with rcrmqobj.
- On z/OS shared queues, delete the queue and define it again so the structure and list headers are set up.
- If no recovery is possible, delete and redefine the object, or restore from backup; a queue manager restart may be needed.
Example
Illustrative only; names and values are invented.
MQOPEN failed CompCode=2 Reason=2101 Queue=APP.DATA.QUEUE