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 » Mainframe, CICS, TXSeries » Trigger don't start process

Post new topic  Reply to topic
 Trigger don't start process « View previous topic :: View next topic » 
Author Message
giuly020277
PostPosted: Wed Nov 19, 2008 11:14 pm    Post subject: Trigger don't start process Reply with quote

Centurion

Joined: 07 Aug 2007
Posts: 146
Location: Florence,Italy

Hello,
i need your help (again) about the behaviour of my queues.

in zos (version 1. i have websphere mq foz zos (v. 6.0).
I have two local queue (A and B).
they are both triggered with First.
Queue A's trigger let start a cics transaction called PIPPO while queue B's trigger let start a cics transaction called PLUTO. Both transaction (pippo and pluto) run under the same CICS.

On queue A a job batch put 1000 messages at time while on queue B a web application put message once at time.

Sometimes it happen that :

After job batch have put 1000 messagges on queue A....PIPPO start and process all message (once at time). It take about 30 minutes to process all messages.
In the while PIPPO is running...sometimes web application put messages on queue B ...but trigger don't starts PLUTO. It seems trigger of queue b is blocked. I have to start it manually...if not...messages come on queue B without trigger start PLUTO.
It happen sometimes...not always.

Can someone help me...to understand why this happen?

Thank u all

Giuliano
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Nov 20, 2008 12:49 am    Post subject: Re: Trigger don't start process Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

giuly020277 wrote:
Can someone help me...to understand why this happen?


Clearly while this PIPPO transaction is running the triggering criteria for the other queue are not being met. Make sure the transaction isn't opening (even for browse) queue B. Also ensure that CKTI is still running after PIPPO starts.

Other suggestions are equally valid.

Remember that there are a number of criteria for a trigger event to be raised, and all must be true. In your case, one of them is obviously false intermitantly.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Thu Nov 20, 2008 3:41 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Also make sure that the web that is putting the message to B does not take too long to commit the message.

Your application servicing B should do a get with wait for the time it may take B to commit the message. (q depth changed but message not available)

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
PeterPotkay
PostPosted: Thu Nov 20, 2008 6:26 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

fjb_saper wrote:
Also make sure that the web that is putting the message to B does not take too long to commit the message.

Your application servicing B should do a get with wait for the time it may take B to commit the message. (q depth changed but message not available)

Have fun

While the trigger message may be created immediatly for an uncommited application message landing on a trigger app queue, the trigger message won't be commited until the application message that satisfied the trigger conditions is committed or backed out.

A triggered app does not have to worry about getting triggered only to find the triggering application message uncommitted, although it should be able to handle finding no message because it was rolled back (2033 is not a problem). And it should handle finding other messages that landed subsequent to the one that kicked off the creation of trigger message in the first place, which is the reason IBM committs the trigger message even if the application message that started the process is rolled back (read until 2033).
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
giuly020277
PostPosted: Fri Nov 21, 2008 3:54 am    Post subject: .. Reply with quote

Centurion

Joined: 07 Aug 2007
Posts: 146
Location: Florence,Italy

thank u all for your answer...

i just need to know last thingh.

If pippo is running and processing 1000 messagges...and pluto (for some reason) is not started at the first message arrived on queue B (so many messages are stored on queue B)..... If i have flag trigger interval = 60 sec...after this time...another trigger message is put on initation queue....so pluto start. and pippo? start another pippo or...transaction pippo who is running has locked the queue so another pippo can't start?
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Nov 21, 2008 4:02 am    Post subject: Re: .. Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

giuly020277 wrote:
another trigger message is put on initation queue....so pluto start. and pippo? start another pippo or...transaction pippo who is running has locked the queue so another pippo can't start?


The trigger will start whichever process it's designed to start, but if PIPPO has queue A open and is reading it, no FIRST trigger message will be raised irrespective of anything else. Check out the documentation on triggering.

It's also poor design to have a transaction lock a queue, because you may want another instance running at times of high volume. Unless you have a really bad design with message affinity in it. This is not a good thing, especially in a high volume environment as it doesn't scale
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
giuly020277
PostPosted: Fri Nov 21, 2008 6:09 am    Post subject: Reply with quote

Centurion

Joined: 07 Aug 2007
Posts: 146
Location: Florence,Italy

..i mean....open a queue...not lock...sorry.

Yes.. i wanted to be sure that if trigger interval expire while a transaction is serving a queue..... no other trigger messages are created that start cuncurrent trasactions

Thank u...I'm reading the application programming guide to find where it is written ( i need a proove for my collegs )
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Nov 21, 2008 6:12 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

giuly020277 wrote:
Thank u...I'm reading the application programming guide to find where it is written ( i need a proove for my collegs )


http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/topic/com.ibm.mq.csqzal.doc/fg13860_.htm

Condition 4
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
giuly020277
PostPosted: Fri Nov 21, 2008 6:33 am    Post subject: Reply with quote

Centurion

Joined: 07 Aug 2007
Posts: 146
Location: Florence,Italy

....

i have no words for your help.. THANK U
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 » Mainframe, CICS, TXSeries » Trigger don't start process
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.