You can convert an MRM message to a different code page or encoding, or both. To do this, you should set the CodedCharSetId and Encoding fields in the appropriate output WebSphere® MQ header to the target value. The appropriate WebSphere MQ header is the header that precedes and is adjacent to the output message body.
The data conversion performed is dependent on the simple type of each element:
Boolean schema types: boolean objects are not converted.
DateTime schema types: date, dateTime, gDay, gMonth, gMonthDay, gYear, gYearMonth, time objects are handled as either binary, string, or packed decimals. If a dateTime element is defined as binary, it is not converted. If it is defined as string, it is converted as a string element (see String schema types).. If it is defined as a packed decimal value, it is converted as decimal with Physical Type set to Packed Decimal (see Decimal schema types).
Decimal schema types: decimal, integer, negativeInteger, nonNegativeInteger, nonPositiveInteger, positiveInteger objects with Physical Type set to External Decimal are converted to the target CodedCharSetId. Elements with other Physical Type settings are converted to the target Encoding.
Float schema types: double, float objects with Physical Type set to External Decimal are converted to the target CodedCharSetId. Elements with other Physical Type settings are converted to the target Encoding.
Integer schema types: byte, int, long, short, unsignedByte, unsignedInt, unsignedLong, unsignedShort objects with Physical Type set to External Decimal are converted to the target CodedCharSetId. Elements with other Physical Type settings are converted to the target Encoding.
String schema types: anyURI, duration, ENTITIES, ENTITY, ID, IDREF, IDREFS, language, Name, NCName, NMTOKEN, NMTOKENS, normalizedString, NOTATION, QName, string, token objects are converted to the target CodedCharSetId (the length of an object that has Physical Type of Length Encoded String 2 is converted to the target Encoding).