| Author |
Message
|
| kiran26 |
 Posted: Tue Sep 17, 2002 9:16 pm Post subject: Grouping and Sequencing |
 |
|
Acolyte
Joined: 06 Feb 2002
Posts: 69
|
Hi,
I am sending messages to my message flow in a group.And my message flow after processing messages will put them into a AS/400 queue.On as/400 a application is reading messages depanding on sequence no., and will terminate when it see's a final message flag on the message in the group.
Say when i send 25 messages in group and two went to failure queue, so 23 messages will be on the as/400 queue.So when our as/400 application trys to read the messages its ends in middle saying the sequencing is not correct.Can any one suggest me in this how to work with grouping & sequencing in MQSI.
Thanks
vishnu |
|
| Back to top |
|
 |
| lbrett |
| Posted: Wed Sep 18, 2002 4:32 am Post subject: |
|
|
Novice
Joined: 24 Jan 2002
Posts: 20
|
| Check commit by message group (under the advanced tab) on the input node and set transaction mode (under the advanced tab) of the as/400 output node to yes. |
|
| Back to top |
|
|
| kiran26 |
| Posted: Wed Sep 18, 2002 7:09 am Post subject: |
|
|
Acolyte
Joined: 06 Feb 2002
Posts: 69
|
Hi,
Thanks very much for your reply.Can u tell me in which queue the messages will be in.
Thanks
vishnu |
|
| Back to top |
|
|
| kiran26 |
| Posted: Wed Sep 18, 2002 7:36 am Post subject: |
|
|
Acolyte
Joined: 06 Feb 2002
Posts: 69
|
| I am getting 2110 reason code error and messages r going to DEAD-LETTER QUEUE from the AS/400 side. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Sep 18, 2002 7:36 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
When there is no error during processing of these messages, all messages will be sent to the output queue.
If any one of the message fails during processing, all messages will be sent to the failure queue.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| kiran26 |
| Posted: Wed Sep 18, 2002 7:41 am Post subject: |
|
|
Acolyte
Joined: 06 Feb 2002
Posts: 69
|
Kiran,
I have done all,
Check commit by message group (under the advanced tab) on the input node and set transaction mode (under the advanced tab) of the as/400 output node to yes.
But when i send messages to the NT system some are going to O/P queue and some r going to failure queue.all messages will be sent to the failure queue is not happing. If i send messages to AS/400 queue i am getting 2110 error and all messages are going to DEAD-LETTER queue.Can u help on this.........
thanks
vishnu |
|
| Back to top |
|
|
| philip.baker |
| Posted: Wed Sep 18, 2002 8:01 am Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
Hi,
Where the messages go depends on how your flow is setup and how some MQSeries settings are set. I will assume that MQSI is the coordinator of messages as opposed to setting up MQSeries to control globally-coordinated transactions.
If you have a failed message within the group, it will rollback through the flow towards the InputNode. If you have nothing wired to the Failure terminal of the InputNode and no Backout Requeue queue set on the Input queue and no Default DLQ on the QMGR, the message will be put back on the Input Queue and the Backout Count on the message will increase each time the flow tries to take the failed message off the queue. None of the following messages within the group after the failed one will be read off the queue.
If a Backout Requeue queue is set on the Input queue, once the message retry exceeds the Backout Count, the message will go to the queue specified by the Backout Requeue queue setting. Subsequent (error-free)messages within the group will be processed and placed on the specified Output queue defined in the Message Flow if Transaction Mode is not set to 'Yes' even though 'Commit by Message Group' is checked in the Input Node.
If a Backout Requeue Queue is not set on the Input Queue and nothing is wired to the Failure terminal of the Input Node but a Default Dead Letter Queue is set on the QMGR, your failed messages will make it to the DLQ.
There are a few more details involved with getting failed messages within a message group to work as expected. (Meaning - if one message within the group fails, all previous messages should be rolled-back and subsequent messages should not be processed.)
Hope this does NOT confuse the issue for you.
Regards,
Phil
Last edited by philip.baker on Wed Sep 18, 2002 1:03 pm; edited 1 time in total |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Sep 18, 2002 11:46 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Vishnu,
I was hoping that all the messages belonging to a particular group will be processed in a single UOW, but it appears that it is not happening. Looks like Commit By Message Group option in MQInput node is not implemented. I have never used this option before.
If you don't want your AS/400 application to process incomplete messages, you could specify MQGMO_COMPLETE_MESSAGE option in MQGET.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| lbrett |
| Posted: Wed Sep 18, 2002 11:56 am Post subject: |
|
|
Novice
Joined: 24 Jan 2002
Posts: 20
|
| The commit by message group will process message groups as a uow, if the output node is transactional. I can't believe that by setting these two options on the nodes would cause you to get a 2110. Are you sure you have not received this before? Also can you confirm the number of committed messages on the AS/400 queue durning this scenario? Are you getting all or some of the messages? Remember that uncommitted messages may appear on the queue (i.e. in the curdepth stats), but until those messages are committed then they are not available to you or your application. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Sep 18, 2002 12:10 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
lbrett,
| lbrett wrote: |
The commit by message group will process message groups as a uow, if the output node is transactional.
|
In my testing I found that the Messages are committed when they are written to the output queue (before the last message is processed). If any message in the group fails during processing, it follows the failure path in the message flow. Other messages get committed to the output queue. This is not expected behavior. 
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| philip.baker |
| Posted: Wed Sep 18, 2002 1:12 pm Post subject: |
|
|
Voyager
Joined: 21 Mar 2002
Posts: 77
Location: Baker Systems Consulting, Inc. - Tampa
|
I have found (testing with MQSI V2.0.1 and V2.0.2) that MQSI coordinated transactions using message groups do not rollback messages within the group as MQSeries does.
I was unable to test if using MQSeries to globally-coordinate the MQSI transaction would give different (e.g. better) results. I would guess not because MQSI has to relay the info to MQ for MQ to properly rollback the transaction.
Phil |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Sep 18, 2002 1:28 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Phil,
Thanks for the update. I did my testing on WMQI 2.1 CSD2.
It would be great if someone can test this in WMQI 2.1 CSD3 and confirm the results.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
