MQRC 2091: Transmission queue type error

What it means

A remote put or open needs a suitable local transmission queue. Reason 2091 identifies a type mismatch: the selected name does not identify a local queue. IBM documents resolution through an explicit XmitQName and through remote queue-manager names.

Do not confuse this with 2092. A queue can be local yet still have the wrong Usage attribute; that is a different configuration problem.

A troubleshooting example

A deployment creates PAYMENTS.XMIT as a remote definition instead of a local transmission queue. The producer opens a remote destination whose XMITQ points there and receives 2091. Compare object types before changing channel state. Correct the definition under the queue owner's plan, then send a uniquely identifiable test message and follow it through to the receiving application. Checking only the existence of PAYMENTS.XMIT would have missed the type error.

Common causes

• A remote-queue definition names an alias or remote definition where a local transmission queue is required.
• An empty XMITQ causes fallback resolution through a queue-manager name that identifies the wrong queue type.
• A deployment script creates a definition with the expected name but the wrong object type.

How to find the problem

1. Capture ObjectName and ObjectQMgrName from MQOD and identify the local remote-queue definition used by the call.
2. Display its RNAME, RQMNAME and XMITQ values. Follow the selected transmission name to its actual definition type.
3. Compare definitions with the intended routing design and a working environment. A matching name does not prove matching object type.
4. Check whether the error occurred before messages entered the transmission queue. Avoid restarting channels as the first response to a definition mismatch.

How to fix it

• Correct the route to use the approved local transmission queue. Have the administrator review naming and definitions together.
• If creating a new transmission queue is necessary, use a change plan that preserves existing messages and channel relationships.
• Validate routing with one approved test message and verify arrival on the remote destination. A successful local open does not prove end-to-end delivery.

What it looks like

Illustrative diagnostic notes; not an IBM message template.
DISPLAY QREMOTE(APP.OUT) RNAME RQMNAME XMITQ
Resolve XMITQ to its definition type.
Reason=2091: selected transmission destination is not local.

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.