MQ Reason Code 2195 when moving MQ messages

When dealing with complex messages that need to be moved and copied you should change your Infrared360 IBM Queue Manager connection setting from "Additional Message GET options" to "Force RFH2".

This setting is located on the connection modify screen under the 'Message Related' tab. We recently had a customer that could not upload a message from a file that was downloaded from Infrared360, they were receiving a MQ reason code 2195 during the upload process. The message with the issue had both RFH2 headers and message properties. This condition appears to occur when both RFH2 and properties exist in the message. In our testing this only occurs on certain messages of this type not all, we were never able to reproduce this issue generating the same type of message in our lab environment. We are in the process of adjusting the message move / copy functionality to get messages using "Force RFH2" automatically to avoid customers needing to make this adjustment in the future.

This GET setting is the same setting that the IBM utility application 'dmpmqmsg' is using under the covers. In the meantime, you should make this adjustment to your connections to ensure safe move / copy message processing.

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Object types in Infrared360 database

Below are the constants for object types in the Infrared360 database QUEUE = 2 CHANNEL = 3...

Alert not firing for Message Age

https://www.ibm.com/docs/en/itcam-app-mgr/7.2.0?topic=tpwmma-oldest-msg-age-short-term-queue-time...

Clearing log files: using File service

Clear Log Functionality – using the File Service Common issues when using web applications such...

Emulation mode

This should be in the inline doc --- search for 'emulation' (no quotes) but basically it's a ROLE...

Making Channel Authorization changes with Infrared360

Channel Authentication (MQSC Commands)   To allow channel authentication records to control...