MQSeries.net :: View topic

Lo · Posted: Mon May 28, 2007 9:03 am Post subject:

Upgrading from 2.1 to version 6.0 problem.

Broker 2.1 was running find with customers sending data in codepage 437, 819 and 420. Broker reformatted for Mainframe backend. Mainframe sent back reply with codepage 420 to broker and sent back to customers of codepage 437,819 and 420.

Once upgraded to 6.0 Broker complains with Unconvertable character when it tries to send back to 437 and 819 clients.

Using RFHUtil, i can put using 1208 and receive back proper reply. If i use 437,819,1252.1256 i get the problem.

The data is only blowing when local characters (arabic) are inside the reply and only to windows ccsid's.

This is the data (i deleted some for brevity).

(0x03000000):Line = 312
(0x03000000):Function = 'ImbConverterCPP::internalFromUnicode'
(0x03000000):Type = ''
(0x03000000):Name = ''
(0x03000000):Label = ''
(0x03000000):Catalog = 'BIPv600'
(0x03000000):Severity = 3
(0x03000000):Number = 2136
(0x03000000):Text = 'Unconvertable character'
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = '2706'
)
(0x01000000):Insert = (
(0x03000000):Type = 5
(0x03000000):Text = '3c0053004100...1248 chars deleted...4e0061006d0065003e002706a3fee3fe2f062000200020002706fbfea3fee3fe2f063c002f00...360 chars deleted...530047003e00'
)
(0x01000000):Insert = (
(0x03000000):Type = 2
(0x03000000):Text = '437'
)

I've heard broker 6 has been setup to be more strict about its validation. The problem is some customers do not care whther they could view the local data so it wasnt important for them. I would rather the broker didnt complain so much, and forward on the data.

Apart from telling the customers to send only in 1208 and 420 what else can i do.

Thanks.