Losing message body

[wilkenpa]

We are running MQ version 4.2.1 with the latest ptfs on AS400 4.3 and it is sending messages to HPUX 11 running MQ version 5.1 csd 5. We are sending messages and the header info is getting to the queue on the HP side but the message body is lost. Anybody else run into this problem or have any suggestions.

Thanks
Paul

 

[smeridew]

What you are suggesting is not really possible, unless the original message is empty, or the receiving app just can't interpret the message. Make sure you are specifying MQFMT_STRING in the format field of the message header, to ensure proper data conversion. Also, make sure you have CONVERT(YES) on the sender channel (is AS400 EDCDIC?)

I'd suggest stopping your channel and looking in the transmission queue to see if the original message data is populated on the AS400 side first.

Use something like MQ Explorer to view the message on the HP-UX machine (yes, you can install MQ for NT on your desktop and peer into an HP-UX queue manager!). This way you cansee if the message data is really there, or if your receiving app just can't see it.

Cheers,

Scott Meridew
MQ Squared Inc.

http://www.mqsquared.com

Scott Meridew
Certified MQSeries Specialist,MCSE
MQ Squared Inc.

http://www.mqsquared.com

 

[wilkenpa]

We have taken periodic looks at the transmit queue on the 400 side and have not seen messages with 0 length. We have also take a look on the HP side and have found a few hundred out of a thousand with 0 length messages. We have not been able to match up msg ids with one on the 400 having a message length and stuff on the hp side with out message length. If we slow things down like that the messages go with no problem. We also are doing this in our test environment and it works fine. The only difference is that the AS400 version is 4.4 and not 4.3. I wouldn't think this is possible either but I cannot disproved it because when I look at the transmit queue the messaged have a length and it works with the same program in our test environment.

-Paul

 

[smeridew]

Paul,

Are you using end-to-end guaranteed message delivery? In other words, are you using fastpath bindings on your channels? The integrity of messages is compromised if you do use this option, so be careful.

I'm also curious to understand how you know the messages are zero length. Can you see them in the queue as zero length messages? Or is the program that reads the queue just reporting this? I guess what I'd like to know is if you have ever seen a non-zero length mesage in a transmit queue,and then the corresponding message in the destination queue with zero length.

another question: are you sure no other program is creating these messages? Check the applicaiton ID of the MQMD to make sure these messages are coming from the correct app.

I'd try having the sending app log its messages before sending them to see if you can match up the zero-length messages. This will at least give you something to look at that might help you decipher why only certain messages are zero-length. (i.e. perhaps a special character is causing MQ to be unable to convert the data)

Cheers,

Scott.
Scott Meridew
Certified MQSeries Specialist,MCSE
MQ Squared Inc.

http://www.mqsquared.com