MQRC 2082: Alias target queue unknown

What it means

An alias queue (QALIAS) is a second name for another queue or a topic. Its TARGET attribute, called BaseQName in the MQI and TARGQ in older MQSC, names the real object. When an application opens the alias, the queue manager looks up that target. If it can't find a queue by that name, the open fails with MQCC_FAILED and reason 2082. The error is about the alias's target, not about the alias itself, which is why it differs from 2085.

MQ doesn't check the target when the alias is defined. An alias can sit for months pointing at a queue that was never created, renamed or deleted, and fail only when someone uses it.

Clusters cause many 2082s. Aliases are often used to give a local name to a cluster queue hosted elsewhere. If this queue manager hasn't learned about that cluster queue, or the application names its own queue manager in ObjectQMgrName so the lookup stays local, the target can't be resolved. IBM notes the code can also appear while a REFRESH CLUSTER is running. The same reason code identifies the Unknown Alias Base Queue event.

Common causes

• The target queue named in the alias's TARGET attribute was never defined, was deleted, or was renamed.
• A typo or wrong case in TARGET. Unquoted names in MQSC are folded to uppercase, so a target defined in lowercase with quotes is a different queue.
• The target is a cluster queue that this queue manager doesn't know about yet, for example because it isn't in the cluster or the cluster definitions haven't reached it.
• The application sets ObjectQMgrName to its own queue manager, so the queue manager looks only locally for a target that lives on another cluster member. For JMS, the QMANAGER property of the queue object has the same effect.
• A REFRESH CLUSTER is in progress and cluster information is being rebuilt.

How to find the problem

1. Display the alias with DISPLAY QALIAS(ORDERS.ALIAS) TARGET TARGTYPE, then its target with DISPLAY QUEUE(target). A 'not found' response confirms the cause.
2. For a cluster target, run DISPLAY QCLUSTER(target) on the queue manager the application connects to. If nothing comes back, this queue manager doesn't know about the cluster queue.
3. Check the application's ObjectQMgrName, or the JMS queue's QMANAGER property or queue URI, for a queue manager name.
4. If queue manager events are on, an Unknown Alias Base Queue event on SYSTEM.ADMIN.QMGR.EVENT names the alias and target.

How to fix it

• Define the missing target queue, or change the alias with ALTER QALIAS(ORDERS.ALIAS) TARGET(ORDERS.IN) to point at the right one.
• Leave ObjectQMgrName blank so clustering can choose the destination. In JMS, set QMANAGER to an empty string.
• Fix cluster membership so the queue manager learns about the target, for example by checking its cluster-sender and cluster-receiver channels.
• Open cluster queues for output only. A remote instance of a cluster queue can't be read, so get options fail.

What it looks like

JMSWMQ2008: Failed to open MQ queue 'ORDERS.ALIAS'.
JMSCMQ0001: IBM MQ call failed with compcode '2' ('MQCC_FAILED') reason '2082' ('MQRC_UNKNOWN_ALIAS_BASE_Q').

Technical reviewer: Albert Joseph, WND Software.

Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s MQ documentation for your version.