MQRC 2027: Reply-to queue missing

What it means

MQPUT or MQPUT1 was asked to send a message whose settings require somewhere to return a reply or report. The descriptor supplies no reply queue. IBM identifies two triggers: MQMT_REQUEST and report requests in the MQMD Report field.

A destination queue for the outgoing business message does not automatically become its reply queue. The sender must supply a return destination appropriate to the application design.

A troubleshooting example

A support change enables exception reports on outgoing payment requests. The normal flow previously used no replies, so ReplyToQ remains blank. Every put now fails with 2027. Compare the before-and-after descriptor settings and choose an approved report queue. Send a test request that deliberately triggers a report and confirm the sender can consume it. Checking only that the outbound put succeeds would leave the new report path untested.

Common causes

• The application changes a message from a datagram to a request without populating ReplyToQ.
• A diagnostic report option is enabled while the existing descriptor has no return address.
• A dynamic reply queue was created, but its actual name was not copied into the outgoing descriptor.

How to find the problem

1. Inspect MsgType, Report, ReplyToQ and ReplyToQMgr immediately before the failing put. Log descriptor settings separately from payload text.
2. Trace the code path that enables request or report behavior. Compare it with a successful datagram path using the same destination.
3. If a model queue is involved, distinguish the model's name from the created dynamic queue name returned by MQOPEN.
4. Confirm the receiver's reply contract and the sender's receive setup. A nonblank but unusable return address only moves the failure later.

How to fix it

• Set ReplyToQ to the real queue that will receive the reply or report. Use the actual created name when using a dynamic queue.
• If the application does not need replies or reports, correct the message type or report configuration according to its interface contract.
• Test an end-to-end reply, including identifiers, queue lifetime and permissions. Retrying the original unchanged descriptor will reproduce 2027.

What it looks like

Illustrative diagnostic notes; not an IBM message template.
MQMD.MsgType = MQMT_REQUEST
MQMD.ReplyToQ = blanks
MQPUT Reason=2027
Set a real return destination before retry.

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.