MQSeries.net :: View topic

Carlos PantÃn

Hi all gurus.

We have a Lotus Domino app on a NT machine using MQLSX (lotus script extension) annd a MQClient to connect to an MQ Server on OS2 that connects to an MQ Server on a OS390. The application works fine since 1998.

We need to shut the OS2 server off. We want to connect directly from the MQLSX + MQ Client NT to the OS/390 MQ server without modifiyng the OS/390 source code. We have made similar changes migrating some Java applications on AIX changing the AIX MQ server to the OS/390 one. We only needed to change Character set of the message and everything worked fine. The Character set conversion was made by the java client.

The problem we have with MQLSX is that we must convert the message in the client side to avoid modifiyng the source code on the OS/390 server. We use the character set properties of the message and we use writestring and readstring methods to store the Lotus data on the MQ Messase. The fact is that we see the data traveling for the network ( packet sniffer) and the contents seems to be fine (EBCDIC DATA), but in the server we don't see anything. We have a trigger ( depth 1) on the incomming queue ant the associated transaction is never raised.

We compare the packets of the java client and the Lotus one on the network and I see that the message length of the MQ message is encoded differently : one is big endian ant the other is little endian. The message we send is only a string without numbers (needs no encoding for the data), and we cannot modify the encoding for the message header.

Another information:

MQSERVER variable properly set. MQCCSID set to 850 (Latin). Character code conversion for the message 284 (Spanish)

Any clues, ideas, suggestions, ...

Thank you!!

Carlos