ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » Triggering

Post new topic  Reply to topic
 Triggering « View previous topic :: View next topic » 
Author Message
vandana
PostPosted: Thu Dec 13, 2001 11:37 pm    Post subject: Reply with quote

Acolyte

Joined: 01 Dec 2001
Posts: 74

I'm working on MQSeries 5.2 installed nt 4.0.
I've the following queries
1)in the mq explorer i see the trigger
type as first,every and none but
not depth.
as a result i'm not able to see the
effect of trigger type every.
what could be the reason ?

2)does the QM has to be restarted if the
properties for triggering have been changed
for any of its local queues?
eg.from trigger-type every to
trigger-type first?

i could not see the change unless i restarted the queuemanager.
what is the reason?

3)I have a queuemanager in which i have a local queue for which triggering is enabled
and trigger type is set to first.
after starting the trigger monitor
when i put a message in the queue using amqsput the triggering occurs for every
message put.
i presume that the triggering should
occur only for the first message .
is that correct?
the trigger interval for the QM is the default (i.e 999 999 999 milliseconds)

Thanks,
vandana


_________________


[ This Message was edited by: vandana on 2001-12-14 00:01 ]

[ This Message was edited by: vandana on 2001-12-14 00:05 ]
Back to top
View user's profile Send private message
EddieA
PostPosted: Fri Dec 14, 2001 9:51 am    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

1) Did you use the scroll buttons.

2) No. But be aware that if you change to trigger type first and there are already messages on the queue, then the trigger will not fire.

3) The triggering will occur when the queue depth goes from 0 to 1. If the depth is zero when the message is put, then it will cause the trigger to fire. Take a look at the Application Programmers Guide. It has a complete section on triggering that lists all the conditions that must be true for a trigger to fire.

Cheers,

_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
vandana
PostPosted: Sun Dec 16, 2001 9:08 pm    Post subject: Reply with quote

Acolyte

Joined: 01 Dec 2001
Posts: 74

1) yes i did use the scroll buttons.
but i see trigger type as first,every and none
but not depth.could it be a problem because
i'm working on an evaluation copy.

2)I did refer to the appl guide which says
that trigger type first will fire when the
trigger depth changes from 0 to 1.this does happen but subsequently it triggers for every message put?why is that so?

3)what is trigger data?

Thanks
vandana

_________________


[ This Message was edited by: vandana on 2001-12-16 23:00 ]
Back to top
View user's profile Send private message
EddieA
PostPosted: Mon Dec 17, 2001 6:27 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles

1) When I open the list for trigger type, I see Every, First, and None. I have to use the scroll bar, on the right of the list, to move up the list to see Depth. The evaluation copy should not affect this at all.

2) If every message is causing the trigger to fire on a trigger type of First, then the sequence of events must be something like:

a) Message arrives on queue.
b) Application gets triggered and starts.
c) Application opens Queue.
d) Application reads message.
e) Application closes Queue.
f) Application ends.
g) Message arrives on queue.
h) Application gets triggered.
etc. etc.

If the 2nd message arrives on the queue BEFORE e, then the second trigger will not occur. If it arrives after e (as shown above), then the application would be triggered again, even if the first instance is still running.

3) 'Trigger Data' is one of the fields passed in the MQTM (Trigger Message) to the trigger monitor program. It's filled in with the value from the TRIGDATA attribute of the queue that caused the trigger message to be written.

Cheers,

_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » Triggering
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.