| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| same subscription, different formats on Win vs iSeries |
« View previous topic :: View next topic » |
| Author |
Message
|
| boos |
 Posted: Mon Aug 15, 2016 8:02 am Post subject: same subscription, different formats on Win vs iSeries |
 |
|
Apprentice
Joined: 27 Jan 2004
Posts: 37
Location: Netherlands
|
I've got an alias (queue) which is in reality an alias for a topic (on windows platform, MQ v7.5.0.4)
(reason for this is to duplicate the message to 2 queues without modification for the putting application or the need to change from a PUT to a PUB)
one subscription stays on the windows platform (local queue) the other subscription goes to a remote queue that ends up on an iSeries machine (As400, MQ v7.1.0.7)
both subscription are similar and have no explicit PSPROP property defined, so use the default PSPROP(MSGPROP)
the message is written as MQSTR (MQ FORMAT) and I expect the property to be propagated to the resulting messages of both subscriptions.
But only the message on the windows queue is as expected in MQSTR format. The message on de iSeries is in MQHRF2 format 
On the iSeries we can not process these MQHRF2 messages (Cobol doesn't play nice with variable length header JMS messages).
I've fixed this with de subscription for the remote queue (towards the iSeries) setting to PSPROP(NONE), now the message on the iSeries is as expected in MQSTR format.
I would expect MQseries to behave the same on the different platforms (maybe only a bit different on z/OS).
Anyone have an explantaion for this different MQ-FORMAT behaviour on different platforms even when PSPROP is the same ?
(or is it not the platform but difference in MQ versions ?)
P.S. when the same messeage is PUT on the remote queue (without the Topic/Sub) the message stays ofcourse normal in the same MQSTR format. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Aug 15, 2016 8:04 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You have different versions on each platform...
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Aug 18, 2016 3:25 pm Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
The main difference that comes to mind is the fact that one message will go over a channel and one will not. The channel will be doing a get from the transmission queue and flattening the properties into an RFH2 in order to send them over the channel to the remote system.
I suspect if you have the Windows message go over a channel too, you would have seen the same behaviour.
There are two ways to fix this, you have already found one PSPROP(NONE) on the subscription. The other would have been to look at PROPCTL on the channel.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
