|
Stewart,
I've also seen Candle throw out
alerts about the channel in doubt status. What I learned was that everytime MQ
attempts to start a channel there is small period of time when the channel will
be in doubt. This occurs as the MCA's work through their hand shaking. I was not
able to figure out though why Candle seemed to catch some of these situations
and not others. The only effective way I found to stop Candle from sending the
alerts was to disable the situation in Candle . I still have the Channel Stopped
situation being monitored by Candle and that has been sufficient for my
purposes.
Don Thomas -----Original Message-----
From: Herd, Stewart [mailto:[EMAIL PROTECTED] Sent: Friday, March 21, 2003 11:23 AM To: [EMAIL PROTECTED] Subject: Candle Command Centre and MQSeries
First let me explain that in the MTSP QMGR we have MQ channels going out to:
AAR_MTSP.AAR_AARP AAR_MTSP.AAR_MTST AAR_MTSP.CCRA_TITAN AAR_MTSP.CNR_MCP2 AAR_MTSP.CPR_MQP2 MTSP.TO.MQOHUXP1.BIN MTSP.USCS_MQB1 SGRC.MTSP.ZCC1
All except the top 2 are in remote networks. These are all SNA except for the Sun Solaris. I have the batch size set to 500 for the channels to the other in-house QMGRs as the volume is very high. The volume to MTST is not high, though.
If you look inside the CCC task CANSCMSA at the DD RKLVLOG, you can see the activity. The issue is that the CCC is sending out false channel indoubt alerts, and I think they are always for the high activity channels between MTSP and AARP.
Sometimes the indoubt period is perceived to be short, but here is one that is not: 09:48:09.14 KO41041 Enterprise situation MQSeries_Channels_Indoubt:MTSP:ASYS:MQESA is true. 09:53:09.11 KO41042 Enterprise situation MQSeries_Channels_Indoubt:MTSP:ASYS:MQESA is no longer true.
From this message, you cannot know which channel it MTSP it was. These are showing up as red button alerts on the CCC monitor. When one of these long ones occurs, you can look at MQ with the MQ panel, and the channel is NOT in an indoubt status. I have turned off the channel events going to 'SYSTEM.ADMIN.CHANNEL.EVENT', which the CCC reads, but it is gather this info by observing the QMGR in a non-intrusive way. That's what Candle calls it.
So, this is the issue. Operations is being bombarded with channel indoubt alerts, which in my opinion are not actually occurring.
Has anyone had a similar experience or any ideas?
Stewart Herd Senior Software Engineer Systems Engineering Services ACS NSC Campus Loughmahon Technology Park Cork Ireland Office.... +353 21 2309331 Mobile.... +353 86 1713777
|
- Candle Command Centre and MQSeries Herd, Stewart
- Re: Candle Command Centre and MQSeries Rick Tsujimoto
- Re: Candle Command Centre and MQSeries Thomas, Don
- Re: Candle Command Centre and MQSeries Glen Shubert
- Re: Candle Command Centre and MQSeries Jan van Kemenade
- Re: Candle Command Centre and MQSeries Herd, Stewart
