# MQRC 2079: Truncated message accepted Source: https://wndsoftware.com/mainframe-errors/mqrc-2079 ### MQRC 2079: Truncated message accepted MQRC 2079 warns that MQGET accepted a truncated message. The message may already be removed, so preserve transaction context before trying again. #### Other names for this code Also written as `RC2079`, `reason code 2079`, `MQ error 2079`, `MQRC_TRUNCATED_MSG_ACCEPTED`, `081F`, `0x081F`. ### What it means The buffer was too small, but MQGMO_ACCEPT_TRUNCATED_MSG allowed the get to complete. The returned buffer holds the part that fits, while DataLength describes the original length. A destructive get removes the message subject to unit-of-work behavior; a browse advances its cursor. IBM classifies the result as MQCC_WARNING. Treating it as an ordinary failed get can lose the distinction between consumed data and a message still available to retry. #### A troubleshooting example A consumer expects JSON but accepts truncated gets by default. A larger message returns 2079, then parsing fails because the final bytes are missing. A second get retrieves a different message because the first one was already consumed outside syncpoint. Fix the buffer policy and warning classification together. A regression test should verify the message's availability after a too-small-buffer result and should reject partial business data explicitly, rather than depending on a parser failure to notice truncation. ### Common causes - The program intentionally accepts partial messages for a preview or inspection feature. - A default get-options mask includes accept-truncated behavior even though the consumer requires the full payload. - Message sizes grew beyond a fixed buffer and the consumer did not inspect warnings. ### How to find the problem - Record BufferLength, returned DataLength, the get options and whether the call browsed or consumed. - Establish whether the get was under syncpoint and whether it was committed or backed out. Preserve the returned partial data safely for diagnosis. - Check the consumer's warning-handling path. Determine whether it parsed or acted on the incomplete payload. - Test with a message just larger than the buffer and verify queue state afterward. Do not infer retention from a generic exception message. ### How to fix it - For full-message processing, remove accept-truncated behavior and implement a supported sizing or retry approach that preserves the message. - If the get was destructive under a transaction, follow the application's approved backout path before expecting the complete message to be available again. - For deliberate previews, mark the data as partial and never send it to business parsers that require the complete document. ### What it looks like ```text Illustrative diagnostic notes; not an IBM message template. MQGET BufferLength=1024 DataLength=4096 CompCode=MQCC_WARNING Reason=2079 MQGMO_ACCEPT_TRUNCATED_MSG was set. Check whether the message was consumed and committed. ``` ### IBM documentation [IBM MQ 9.4: 2079 MQRC_TRUNCATED_MSG_ACCEPTED](https://www.ibm.com/docs/en/ibm-mq/9.4.x?topic=codes-2079-081f-rc2079-mqrc-truncated-msg-accepted). Use the documentation for your installed release. [Report a correction to WND Software](https://wndsoftware.com/contact#message). Technical reviewer: [Albert Joseph](https://wndsoftware.com/authors/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. ### Related codes [MQRC 2080 MQRC_TRUNCATED_MSG_FAILED Read →](https://wndsoftware.com/mainframe-errors/mqrc-2080) [MQRC 2120 MQRC_CONVERTED_MSG_TOO_BIG Read →](https://wndsoftware.com/mainframe-errors/mqrc-2120) [MQRC 2033 MQRC_NO_MSG_AVAILABLE Read →](https://wndsoftware.com/mainframe-errors/mqrc-2033) ### Questions #### Will another MQGET return the complete message? Not necessarily. An accepted destructive get may already have removed it. Check syncpoint and commit state. #### How does 2079 differ from 2080? 2079 accepted truncation and completed with a warning. 2080 reports truncation rejected; its handling and message-retention implications differ. [IBM MQ reason codes](https://wndsoftware.com/mainframe-errors/mq-reason-codes) · [MQRC 2072](https://wndsoftware.com/mainframe-errors/mqrc-2072) · [MQRC 2080](https://wndsoftware.com/mainframe-errors/mqrc-2080) [← All error codes](https://wndsoftware.com/mainframe-errors/)