|
Yeah...the coders are doing the get improperly. Unfortunately, I'm not a
JMS coder either, so I cannot tell you the exact solution. But I do know
that JMS plays games with the correlid and msgid because JMS
compliance requires 48 bytes character but MQ has 24 bytes binary.
That can make a little tricky doing the match when a non-JMS
application is in the loop. When JMS converts messages to/from non_JMS
destinations, it discards/adds an "ID:" prefix and compresses/expands between 48
and 24 bytes.
Usually, if you capture the (JMS) msgID that JMS generates for a
request, allow JMS to transform it for the non_JMS destination, pass
exactly the same MQ msgid back in the correlid, allow JMS to
transform it back then all works well. However, if you are generating
your own corelid's in the then you gotta figure out what JMS is doing
with them. I suggest you setup a test using JMS to
read a message without the correlid matching and then take a look at
the correlid that gets presented to the application. That should give
you some insights on how to properly format the JMS correlid on the
get.
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html |
Title: Message
