MQRC 2111: Source CCSID error

What it means

MQ cannot perform the requested conversion from the source character set. On an MQGET conversion path, IBM documents warning results where data is returned unconverted. Other calls can fail. The API and completion code matter.

Messages with multiple headers can contain separately described data sections. Some sections may be converted and others left unchanged, so use the returned CCSID and Encoding fields rather than assuming one character set describes every byte.

A troubleshooting example

A producer sends UTF-8 text but its descriptor carries a different CCSID inherited from a reused message object. A consumer requests conversion and receives 2111. Compare a controlled payload containing accented characters with its actual bytes and metadata. Fix initialization at the producer, then verify the full round trip. A test containing only digits can look correct under several encodings and fail to reveal the mismatch that later corrupts customer names.

Common causes

• A producer labels data with a CCSID that does not describe the bytes it actually wrote.
• The requested source conversion is not supported by the queue manager or conversion environment.
• An application header uses a character set unsuitable for its defined fields, or a property call relies on an inappropriate application CCSID default.

How to find the problem

1. Capture the API, completion code, source CCSID and relevant Format and Encoding fields. Preserve a safe byte sample from test data.
2. Compare the producer's actual encoding with the descriptor. A readable text editor view can hide incorrect metadata or byte transformations.
3. For compound messages, inspect each header's next-format, CCSID and encoding chain instead of changing only the outer MQMD.
4. Check installed conversion support and the IBM explanation for the specific call. On non-LE z/OS property paths, review explicit application CCSID handling.

How to fix it

• Make producers label bytes accurately. Do not change CCSID metadata alone unless the bytes already match that declaration.
• Use a supported conversion path or explicit application conversion where needed. Keep the original encoding information available for diagnosis.
• Handle warning results without parsing unconverted bytes as the requested target encoding. Test accented characters and multibyte data, not only plain ASCII.

What it looks like

Illustrative diagnostic notes; not an IBM message template.
MQGET with MQGMO_CONVERT
Record CompCode, Reason=2111, returned CCSID and Encoding.
Do not assume returned bytes use the requested character set.

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.