| Author |
Message
|
| naxtell |
 Posted: Wed Feb 10, 2010 8:09 am Post subject: Having trouble configuring a trigger |
 |
|
Novice
Joined: 30 Sep 2003
Posts: 17
|
I'm using MQ v7 in Windows Server 03. When I put a message on my send queue (remote definition) the message is passed to my transmission queue and sits there. The associate Channel remains Inactive and is not triggered to start automatically. If I manually start the channel, the message correctly shows up in the receiving queue on my other queue manager. Since queuing seems to work fine and it seems like only the triggering is the issue, I'll just include the settings that seem to pertain to the triggering process.
[SendQueue]
QName: My.Send.Q
QType: Remote
TransmissionQ: My.Trans.Q
[TransmissionQueue]
QName: My.Trans.Q
Usage: Transmission
Triggering (defaults): control=On, type=First, depth=1, priority=0
TriggerData: My.Send.Channel
InitQ: My.Init.Q
Process: My.Process
[InitiationQueue]
QName: My.Init.Q
QType: Local
[Process]
Name: My.Process
UserData: My.Send.Channel
[Channel]
Type: Sender
TransQ: My.Trans.Q
Do I have to specify something else for the Process or maybe on the Init Q? I've been looking through the documentation on triggering but can't seem to find the missing piece. I've read about the channel initiator. Do I have to change something so that it uses my Init Q?
Thanks for any suggestions,
Nate |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Feb 10, 2010 8:41 am Post subject: Re: Having trouble configuring a trigger |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| naxtell wrote: |
| Do I have to change something so that it uses my Init Q? |
Or better still use the SYSTEM queue provided for the purpose.
I'm also guessing you've used dummy names in your post. If not, I'd question the wisdom of your naming convention for objects....
(but this has nothing directly to do with the trigger firing or not)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| naxtell |
| Posted: Wed Feb 10, 2010 8:56 am Post subject: Re: Having trouble configuring a trigger |
|
|
Novice
Joined: 30 Sep 2003
Posts: 17
|
| Vitor wrote: |
| I'm also guessing you've used dummy names in your post. |
Yeah, I used dummy names to help simplify my question.
| Vitor wrote: |
| Or better still use the SYSTEM queue provided for the purpose. |
So I changed my TransmissionQ's InitQ to SYSTEM.DEFAULT.INITIATION.QUEUE and restarted my Queue Manager to ensure I was starting fresh. I put a message on my sending queue, saw the message transfer to my transmission queue, and checked the channel. The channel remains Inactive. What else do I have to do to use the "SYSTEM queue" that you made reference to.
Thanks,
Nate |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 10, 2010 9:04 am Post subject: Re: Having trouble configuring a trigger |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| naxtell wrote: |
| What else do I have to do to use the "SYSTEM queue" that you made reference to. |
Use the correct one. It's SYSTEM.CHANNEL.INITQ. You'll find this described in the documentation under "channel initiator".
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Feb 10, 2010 9:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Are you running a channel initiatorapplication that monitors the channel initiation queue? runmqchi is the name on midrange mq. It's function in life is to watch for trigger messages arriving on a transmission queue, and then start the channel.
_________________
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 |
|
|
| naxtell |
| Posted: Wed Feb 10, 2010 9:26 am Post subject: |
|
|
Novice
Joined: 30 Sep 2003
Posts: 17
|
Actually, using the correct InitQ name did the trick. I selected the wrong item in the list, confusing the default with the channel specific InitQ. I was also able to delete the Process that I created since I specified the Channel Name in the TransmissionQ's Trigger Data.
Thanks for the help. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 10, 2010 9:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| runmqchi is the name on midrange mq. |
On the version the OP is using, it's a queue manager object but yes, if the channel initiator isn't started the efforts to initiate a channel will prove fruitless.
But the OP did mention the channel initiator and from this I assumed (perhaps wrongly) they were running it rather than admiring it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Feb 10, 2010 10:06 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I've read about the channel initiator. Do I have to change something so that it uses my Init Q? |
Yes, you must start a channel initiator. Your choices are the runmqchi control program, or START CHINIT script command.
_________________
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 |
|
|
| SAFraser |
| Posted: Wed Feb 10, 2010 2:04 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
| One additional note that no one cares about at this point, I suppose, since the OP has got his triggering to work... but, I believe when speciifying TRIGTYPE=first, there is no need to enter a value for DEPTH. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Feb 10, 2010 2:17 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| On the version the OP is using, it's a queue manager object... |
It could be an object (which would be my recommendation); but the OP didn't explicitly state that there is/was an channel initiator application (or object) running.
_________________
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 |
|
|
| naxtell |
| Posted: Thu Feb 11, 2010 4:43 am Post subject: |
|
|
Novice
Joined: 30 Sep 2003
Posts: 17
|
| SAFraser wrote: |
| One additional note that no one cares about at this point, I suppose, since the OP has got his triggering to work... but, I believe when speciifying TRIGTYPE=first, there is no need to enter a value for DEPTH. |
I believe you are correct. With type First, triggering occurs only when the depth of the queue changes from 0 to 1. When I included that property above I was simply listing all the triggering settings from the queues property window and didn't realize at the time that I could have just omitted that setting... |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Feb 11, 2010 9:38 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
IMS, TriggerDepth(1) is the initial value of a QL object.
_________________
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 |
|
|
|
|
