| Author |
Message
|
| alvinlimtc |
 Posted: Thu Feb 02, 2006 7:18 am Post subject: Display channel status |
 |
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
What does it mean when I do a display chstatus(*), and I get :
AMQ8420: Channel Status not found.
Does this mean the channels are Inactive?
This leads to 2 other questions.
I have an MQ cluster and I have define all the cluster sender and cluster receiver channels with a disconnect interval of 0. When I start all the QMs in the cluster, and I do a display chstatus(*) on any QM, I get the above 'Channel Status not found'. Only when a message needs to be sent to a cluster member, will the respective channel status be RUNNING. Any way I can get the cluster channels to be up when I start the QMs instead of being triggered?
Also, after the channel statuses are RUNNING, and with the disconnect interval of 0, after a certain amount of inactivity, I get the 'Channel Status not found' again. Is this the expected behaviour? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Feb 02, 2006 7:28 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
yes, that means they are inactive.
Try "dis chs(*) saved".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Feb 02, 2006 9:17 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You don't have to set triggering for cluster channels. They will start automatically if they need to.
For setting disconnect interval, you need to do it on CLUSRCVR's. See if this helps. |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Thu Feb 02, 2006 5:46 pm Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
Thanks for the replies. Yes, I have set the DISCINT for both CLUSSDR and CLUSRCVR.
Is there a way to ensure the channels are started and RUNNING when the cluster managers are started?
Will try the dis chs(*) saved. But what does this imply?
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Feb 02, 2006 5:57 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| alvinlimtc wrote: |
| Is there a way to ensure the channels are started and RUNNING when the cluster managers are started? |
| vennela wrote: |
| You don't have to set triggering for cluster channels. They will start automatically if they need to. |
| alvinlimtc wrote: |
| Will try the dis chs(*) saved. But what does this imply? |
It shows you the saved status of the channel, rather than the current status.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Feb 02, 2006 6:17 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| Only when a message needs to be sent to a cluster member, will the respective channel status be RUNNING. Any way I can get the cluster channels to be up when I start the QMs instead of being triggered? |
Why? What is the reason you want the cluster channels to come up at qmgr start time?
_________________
-wayne |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Fri Feb 03, 2006 1:32 am Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
Apologies, let me re-phrase :
Is it the normal behaviour that the cluster channels are INACTIVE when the queue manager is first started and only triggered when it is used? i could have sworn that during the initial stages, the channels were in RUNNING states when the queue managers were started. But now it is as I mentioned, INACTIVE (ie. 'Channel status not found') initially.
Executed the dis chs(*) saved, and the reply is that the cluster channels are all 'RUNNING'. But this doesn't tell me much, except the SAVED status was RUNNING, but the current status is INACTIVE. |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Feb 03, 2006 2:39 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
The channels wouldn't be running uness there was a need for them... the needs being:
(1) sending a application message across the channel
(2) informing FR qmgrs about new cluster objects.
(3) communicating queries and responses about cluster objects between FR and PR.s....
_________________
-wayne |
|
| Back to top |
|
|
| alvinlimtc |
| Posted: Fri Feb 03, 2006 4:55 am Post subject: |
|
|
Apprentice
Joined: 22 Dec 2005
Posts: 29
Location: Singapore
|
Great.
One last question for this thread.
What is the purpose of being able to query a channel's SAVED status? From what I read, the saved status is reset during a number of conditions as listed in the Intercomm manual. From these conditions, I would say most of the time the channel's SAVED status would be RUNNING!
So what's the point? |
|
| Back to top |
|
|
| HubertKleinmanns |
| Posted: Fri Feb 03, 2006 5:24 am Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
MQSeries stores channel attributes to logs and to the SYSTEM.CHANNEL.SYNC.QUEUE. MQ needs this attributes (such as sequence number), to restart an inactive channel and synchronize it with the partner (sender <-> receiver).
_________________
Regards
Hubert |
|
| Back to top |
|
|
|
|
