MQ Response with "ñ" character

[Julio Ramos]

Hi Community, i have a Route Native MQ Asertion using a SOAP message for request and response and i´m receiving an latin name with "ñ" character like others latin character but my response is not resolving the ñ character. 
Example:
<SegundoApellido>URE�A</SegundoApellido>

How i can configure to get the correct ,<SegundoApellido>UREÑA</SegundoApellido>.

Thanks,

------------------------------
[Julio C. Ramos]
[DevOps]
[IT Business Solutions DEF]
[City]
------------------------------

[Gerlof Bril]

Julio

My first guess would be to check the parameters in the MQ Message header (MQMD) and check whether you use the option to convert the message when reading a message from a queue.
Especially with XML messages you should check whether the XML encoding matches
1. the payload of the message and
2. the CCSID (codepage) in MQMD.

Furthermore the Format parameter in MQMD should contain the correct value.
- When empty, the message will not be converted.
- When it contains "MQSTR", it will be converted when getting the message (with the convert option).

You can play with these parameters to get the desired outcome when putting and getting messages to and from an MQ queue.
Maybe this helps.

------------------------------
Infra Domain Architect
Achmea IT
Netherlands
------------------------------

[Julio Ramos]

Hi Gerlof and thanks for your reply.

well, i´m using format:MQSTR

Others MQMD i´m setting in response are:
 
characterSet:819
encoding:273

The response payload is:

<?xml version="1.0" encoding ="UTF-16"?>
<SiebelMessage ErrorCode="" ErrorText="Satisfactorio" MessageId="" MesageType="Integration Object" IntObjectName="Report v1" IdSol="">
<ReporteCU>
<ClienteUnico>
<PrimerNombre>Jose </PrimerNombre>
<SegundoNombre></SegundoNombre>
<PrimerApellido>Perez</PrimerApellido>
<SegundoApellido>URE�A</SegundoApellido>
<FechaNacimiento>04/28/1998</FechaNacimiento>
<Sexo>MASCULINO</Sexo>
<EstadoCivil>SOLTERO/A</EstadoCivil>
<CedulaNueva>000000</CedulaNueva>
<StatusCedula>T</StatusCedula>
<cod_nacionalidad></cod_nacionalidad>
<desc_nacionalidad></desc_nacionalidad>
<fecha_expiracion>4/28/2054 12:00:00 AM</fecha_expiracion>
<Telefonos></Telefonos>
<Direcciones></Direcciones>
<PaisNacimiento></PaisNacimiento>
<ScorePredictivo>
<Score>0</Score>
<Causa1></Causa1>
<Causa2></Causa2>
<Causa3></Causa3>
</ScorePredictivo>
<Ocupacion></Ocupacion>
<PaisResidencia></PaisResidencia>
<CiudadResidencia></CiudadResidencia>
<SectorResidencia></SectorResidencia>
<CalleResidencia></CalleResidencia>
<NumeroResidencia></NumeroResidencia>
<TelefonoResidencia></TelefonoResidencia>
<TelefonoCelular></TelefonoCelular>
<PasivosPorSuscriptor>N</PasivosPorSuscriptor>
<Transacciones>N</Transacciones>
</ClienteUnico>
</ReporteCU>
</SiebelMessage>

------------------------------
[Julio C. Ramos]
[DevOps]
[IT Business Solutions DEF]
[City]
------------------------------

[Gerlof Bril]

It all comes down what you want to achieve in the end by using a request/reply pattern. 

OK. Based on this information I do not have a clear answer.

What we typically see in this kind of discussions is 
1. we have to deal with an XML message with encoding, typically UTF8 of UTF16.
2. a CCSID which is attached to the MQMD when putting the message in a MQ Queue.
3. the question whether the CCSID matches the content (XML message and encoding)
4. the question whether you want convert the message when reading from the queue, or not. 
These items determine the MQ settings .

Looking again at your situation.
The only suggestion I can give is to look at your local codepage on the platform reading the message from the MQ queue.
Because it seems the message is converted to a codepage in which the special character is not available....
At least, that is a situation we sometimes encounter when special characters are missing.

Maybe this helps....

------------------------------
Infra Domain Architect
Achmea IT
Netherlands
------------------------------