MQSeries.net :: View topic - Japanese characters problem with fixed length message set

er_pankajgupta84 · Posted: Fri Feb 12, 2010 4:28 pm Post subject:

I understand your point. But as I said its a common utility that we use and its a 2 fold process. First we create one Audit message with n number of details + payload and then we another flow will process that message and do the auditing.

We cannot change existing services.

Btw do you know that Can we specify any CCSID when we convert blob to a string in Java.

For eg: Normally if we want to convert blob to string then we do something like this:

new String((bytes[])inRoot.getLastChild().getLastChild().getValue());

How can i specify a CCSID in this kind of coding. Because when I run this command on data that is not in 1208/819 then i don't get a readable string and reason is very obvious. I am sorry to say that i have never used esql so I have to do this in java itself. I know that in esql we do have that option.

There is lot of dependency on how the data is stored in db if we store it in any other format other than 1208 then it would create problem when I want to reprocess the message by taking payload from the db. If i store it in 1399 then it would not be readable and if I store that in 1208 then data would be readable but I would need to convert data back to 1399 before resending it fro processing otherwise it would fail due to length constraint.