| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XMITQTriggerStatus |
« View previous topic :: View next topic » |
| Author |
Message
|
| jeevan |
 Posted: Wed Jul 16, 2008 9:23 am Post subject: XMITQTriggerStatus |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
In Patrol Operator, we got XMITQ Trigger status off and on over a period of time ( last night). Luckily, the channel were on all the time so it did not impact but need to understand how it happens.
BMC document says that the this means whether the tigger attribute is enabled or disabled. How the attribute of XMITQ gets enabled or diabled automatically?
Any clue ? any suggestion ? It is in prod so I need to figure out.
Thanks a lot |
|
| Back to top |
|
 |
| jeevan |
| Posted: Wed Jul 16, 2008 9:39 am Post subject: Re: XMITQTriggerStatus |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
[quote="jeevan"]In Patrol Operator, we got XMITQ Trigger status off and on over a period of time ( last night). Luckily, the channel were on all the time so it did not impact but need to understand how it happens.
BMC document says that the this means whether the tigger attribute is enabled or disabled. How the attribute of XMITQ gets enabled or diabled automatically?
I would like to add:
There is no clue in MQ log and no FDC file. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jul 16, 2008 10:10 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
MQ working as designed. Go look at an XMITQ for a channel that is not running. Notice the Alt Date and Alt Time. Now drop a message that causes the channel to trigger. Go look at the XMITQ's Alt Date and TIme again. See, it changes every time the channel starts ups. As the channel goes thru its various stages its manipulating the XMITQ. Its probably touching the trigger attribute. It definitly touches the Get Inhibit attribute when the channel goes retrying.
I don't think you should be monitoring for an XMITQ's trigger attribute.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jeevan |
| Posted: Wed Jul 16, 2008 10:18 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| PeterPotkay wrote: |
MQ working as designed. Go look at an XMITQ for a channel that is not running. Notice the Alt Date and Alt Time. Now drop a message that causes the channel to trigger. Go look at the XMITQ's Alt Date and TIme again. See, it changes every time the channel starts ups. As the channel goes thru its various stages its manipulating the XMITQ. Its probably touching the trigger attribute. It definitly touches the Get Inhibit attribute when the channel goes retrying.
I don't think you should be monitoring for an XMITQ's trigger attribute. |
The patrol Operator generates an alarm. It is automatic setup ( not sure, someone has done alredy, I need to check whther it is automatic or someone has setup). But I have to dealt with the alarm.
In fact, the trigger attribute has enabled now, but I am getting the false alarm. It may be patrol incorrect information.
thanks a lot |
|
| 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
|
|
|
|
