MQSeries.net :: View topic - Swich Direct MQ call to remote MQ call-Msg sequence disturbd

DTechBuddy · Posted: Mon Jun 20, 2011 6:56 am Post subject:

An application makes direct Mainframe call.
Here the application directly puts message on A queue of mainframe queue manager (MQM), it gets triggered by transaction Z, and sends response to B queue on MQM.

Now, we want to route their calls via the Remote queue manager (RQM).
So, we will have :-
Message fired at queue C (Queue Remote) on RQM pointing to A (Queue Local) on MQM, and triggered by transaction Z, finally pur response at queue D (Queue Remote) on MQM pointing to B (Queue Local) on RQM.

Now here's the issue description :-
When this application fires the message, it actually internally gets fired as a set of two messages : X Bytes Header and Y Bytes payload.
The transaction program at the Mainframe is expecting these messages in exact sequence, i.e. Header first and Payload later.
If the sequence is messed up, then it throws an error message.

1. We set the trigger off at the A queue and saw (using MQ Explorer) that sequence is coming accurate.
2. If I set the trigger off, and allow messages to pile up, and again set the trigger on, then Mainframe transaction picks all the messages in exact sequence and we get valid response. Now, if we continue our testing, again it starts throwing the error response, till I don't set the trigger off.
3. The Message Delivery Sequence on A queue is FIFO, same in Xmit queue.

Any suggestions on where to look further ? ??
My concern is the sequence of messages.

Thanks in advance.