| Author |
Message
|
| swann |
 Posted: Tue Dec 06, 2011 6:39 pm Post subject: Triggering |
 |
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
Hi Friends,
I have two Queue Managers QA and QZ,I have set up channel and application triggering on QZ.The channel triggering i set it on xmitq QZ and application triggering on QZ.LOCAL along with defining the process and a Initiation queue.For the channel triggering i have set the initiation queue as SYSTEM.CHANNEL.INITQ(System defined).My application triggering set up is as follows:
def ql(IQ)
def process(PP) applicationtype(WindowsNT) APPID(C:a.txt)
def ql(QZ.LOCAL) trigtype(depth) trigdepth(5) intiationq(IQ) Process(PP)
I am using windows MQ explorer...and in my application i used (strmqm QX) which is another queue manager).So once the message count hits 5 my triggering should start and would bring up the QX queue manager)
This set up was worked fined for the first time,Then i issued the MQGET to get the messages from the QZ.LOCAL .Now again when the queue depth hits 5 i see the trigger control is going off and when i tried to switch it on manually the application is triggered but the command in application is not working.The runmqtrm monitoring is running in the background.
So friends could you please share what might be the issue........... |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Dec 06, 2011 6:59 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It's an incredibly bad idea to use triggering to issue STRMQM to start a queue manager.
Queue managers should be started and stopped completely independently of application needs. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Dec 06, 2011 9:29 pm Post subject: Re: Triggering |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| swann wrote: |
| ... but the command in application is not working.The runmqtrm monitoring is running in the background. |
You've provide far too little information.
Does the trigger monitor running in background have sufficient authority to start a qmgr? Does it have access to the strmqm command in background?
Run the trigger monitor in foreground. Try it again. Any errors?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Dec 07, 2011 1:34 am Post subject: Re: Triggering |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| swann wrote: |
| ...Now again when the queue depth hits 5 i see the trigger control is going off and when i tried to switch it on manually the application is triggered but the command in application is not working... |
Notwithstanding the comments of my learned colleagues, I suggest you read the relevant section of the Application Programming Guide in relation to application requirements in regard to triggering on depth, i.e. what an application needs to do before ending.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| swann |
| Posted: Wed Dec 07, 2011 4:16 am Post subject: |
|
|
Acolyte
Joined: 21 Jun 2011
Posts: 50
|
| But the application worked perfectly for the first time,it shows that the monitoring have the privilege to start a QM.I dont understand why the trigger contol attribute on QZ.LOCAL goes into off state when a trigger depth of 5 is reached. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 07, 2011 4:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| swann wrote: |
| I dont understand why the trigger contol attribute on QZ.LOCAL goes into off state when a trigger depth of 5 is reached. |
That's because you have not read the documentation.
In general, trigger on depth is not a good idea.
In general, using one queue manager to start another is a very bad idea. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Dec 07, 2011 4:22 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| swann wrote: |
| But the application worked perfectly for the first time,it shows that the monitoring have the privilege to start a QM.I dont understand why the trigger contol attribute on QZ.LOCAL goes into off state when a trigger depth of 5 is reached. |
Once more, and with feeling:
| exerk wrote: |
| ...I suggest you read the relevant section of the Application Programming Guide in relation to application requirements in regard to triggering on depth, i.e. what an application needs to do before ending. |
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Dec 07, 2011 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| swann wrote: |
| .I dont understand why the trigger contol attribute on QZ.LOCAL goes into off state when a trigger depth of 5 is reached. |
Working as intended. I echo the comments of my most worthy associates about reading the documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Dec 07, 2011 5:50 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
With TRIGTYPE(DEPTH), when the trigger fires, triggering is set off by the qmgr. It becomes the responsibility of the application or system administrator to turn triggering back on. This is working as documented.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
