| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| No side-effect after clearing SYSTEM.CHANNEl.SYNCQ ? |
« View previous topic :: View next topic » |
| Author |
Message
|
| issac |
 Posted: Mon Sep 16, 2013 6:41 pm Post subject: No side-effect after clearing SYSTEM.CHANNEl.SYNCQ ? |
 |
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Hello,
Last weekend I had a problem with a clustered QMGR. I had an auto-defined CLUSRCVR channel being INDOUBT(YES). But when I tried:
STOP CHL(TO.MQ1)
RESOLVE CHL(TO.MQ1) ACTION(COMMIT)
It just says the channel is not defined. But this is not the problem I want to address here.
Being frustrated, I searched and found a technote saying clearing SYSTEM.CHANNEL.SYNCQ might work. So I cleared the queue, then restarted the QMGR. I found it does not solve my INDOUBT auto-defined channel problem, but it also has no effect upon CURSEQNO of channels at all.
I was expecting CURSEQNO of channels to mass up after clearing the queue. But after the QMGR is restarted, nothing ever changed. Channels connect with their original sequence numbers.
All the channels on that QMGR are cluster channels, either manual defined or auto defined. Could it be that clearing this queue would simply not effect such channels? Or could anything else go wrong in future due to the clearing action?
Thanks.[/b]
_________________
Bazinga! |
|
| Back to top |
|
 |
| hughson |
| Posted: Fri Sep 27, 2013 7:36 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1916
Location: Bay of Plenty, New Zealand
|
Cluster channels do not have sequence number errors. Since cluster channels are automatically created/deleted for you, we also take care of the sequence numbers for you, receiver always does what the sender tells it to do. Since no V1 MQ product can be connecting to a cluster channel, there is no danger in this.
FYI: Channels go INDOUBT(YES) all the time - every single batch. Normally you don't notice because it is a fleeting state of affairs. Sometimes channels will end due to a network failure whilst they are in this fleeting state of INDOUBT(YES) and then you are more likely to notice. You do not need to do anything to resolve INDOUBT(YES) channels unless the partner is never coming back.
You can decrease the likelihood of a cluster channel ending in the INDOUBT(YES) state by making use of BATCHHB(1) on your cluster channels.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| issac |
| Posted: Sat Sep 28, 2013 5:17 pm Post subject: |
|
|
Disciple
Joined: 02 Oct 2008
Posts: 158
Location: Shanghai
|
Thanks very much for the reply! Got it!
_________________
Bazinga! |
|
| 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
|
|
|
|
