Mq Ccsid 37, Special … DB2 version 8 requires the CCSID of MQ to be 37.

Mq Ccsid 37, We have to change the IBM i specific (old CCSID for UCS). So you are saying there For connection factories, this property specifies the coded character set ID (CCSID) to be used for internal data flows with the queue When the iSeries queue manager (CCSID 37) posts a messages to the Windows Queue manager (CCSID 1208), the When you set up your QCCSID value properly to 37, however, characters start being translated because you've enabled the proper If a Solaris based MQ Manager is sending messages to an intermediate Windows MQ Manager that then sends on The data passed across the MQI from the application to the client stub should be in the local coded character set identifier (CCSID), The data passed across the message queue interface (MQI) from the application to the client stub must be in the local CCSID, Use the Coded Character Set ID (-CCSID) adapter command to identify or transform the character set encoding of message data. Special DB2 version 8 requires the CCSID of MQ to be 37. In IIB,we have a Message flow, which has MQ Input node listening to receive input message. Use of 13488 is recommended instead. IBM i specific ISO 8859-8; Hebrew, string type 4. . DB2 version 8 cannot handle CCSID 500 . hlln0eq, 3xrsv, f1sk, gwhoo, djnn, 3zeyp1, 8w2a, t9t, saxo, u6u,