MQRC 2092: Transmission queue usage error

What it means

The route identifies a local queue, but that queue does not have MQUS_TRANSMISSION usage. IBM documents several resolution paths, including an explicit XmitQName, a queue-manager name used as a queue name, and default resolution.

On z/OS there is also a documented case involving SYSTEM.QSG.TRANSMIT.QUEUE when intra-group queuing is disabled. Apply the explanation for the actual route rather than treating every 2092 as the same edit.

A troubleshooting example

A script creates every local queue with the same defaults, including a queue intended for a sender channel. Its name is correct, but its usage is NORMAL, and remote opens return 2092. Fix the definition recipe and recreate or alter only through the approved administration procedure. Use a test environment containing both the business queue and transmission queue to verify that the route chooses the latter. This catches naming mistakes that a one-queue test would conceal.

Common causes

• A queue intended for transmission was created with ordinary application-queue usage.
• A remote definition points to an application input queue with a similar name.
• A z/OS route selects the queue-sharing-group transmission queue while the required IGQ capability is disabled.

How to find the problem

1. Record the MQOD names and display the local remote definition's routing fields. Establish which queue was selected as the transmission queue.
2. Display the selected local queue's USAGE and compare it with the route design. Preserve the definition and current depth.
3. Check explicit XMITQ versus fallback resolution through RQMNAME. An apparently blank field can still select a queue by another name.
4. For SYSTEM.QSG.TRANSMIT.QUEUE, ask the z/OS administrator to check the documented IGQ condition before changing the route.

How to fix it

• Point the route at the intended transmission queue, or correct the queue definition through the administrator's supported change procedure.
• Do not convert a live business input queue into a transmission queue merely because its name was selected accidentally. Confirm ownership and queued data first.
• Test the entire path and channel configuration after correction. Review deployment scripts so future environments create the intended type and usage consistently.

What it looks like

Illustrative diagnostic notes; not an IBM message template.
DISPLAY QLOCAL(PAYMENTS.XMIT) USAGE CURDEPTH
Observed: USAGE(NORMAL)
Reason=2092: confirm the intended transmission queue.

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.