| Author |
Message
|
| Trainee |
 Posted: Thu Apr 05, 2007 4:19 am Post subject: Transmission queue Trigger Data? |
 |
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Hi
OS: Windows XP service pack1
WMQ:6.0.20
When i was trying to show some demo for Qmgr to Qmgr Connection I defined Remote queue, xmit queue etc and Transmitqueue with out giving any trigger data information in it
It worked for me.I tried couple of times I am sure it worked for me without specifying Sender Channel name in the Trigger Data Information..
OS: Windows XP
WMQ: 6.0
When I tried the same on my laptop with same version(may be no csd is there) it didn't work for me and I just started the Sender Channel then it worked.
Why it behaved differently on different machines. Is it possible that way |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Thu Apr 05, 2007 5:03 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| Trainee |
| Posted: Thu Apr 05, 2007 5:14 am Post subject: |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Yes I am sure,
I was working on that just before posting it here.To make sure I did twice.
Thank you
Trainee |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 05, 2007 1:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You only need to specify the channel name if you have multiple channels sharing the same XMITQ and you want to trigger a specific one.
Note that I have run into the same problem you seem to be having... so check:
- The channel status is not found (INACTIVE)
- The trigger is on (XMITQ)
- The initq is specified as SYSTEM.CHANNEL.INITQ
- The trigger depth is 1
- The trigger priority is 0
- The trigger type is FIRST
- The channel initiator is running
- The channel initiator's queue matches the initq param on the xmitq.
Now put a message on the remote queue and check out what happens in the qmgr's log.
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Apr 05, 2007 2:48 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| fjb_saper wrote: |
| You only need to specify the channel name if you have multiple channels sharing the same XMITQ and you want to trigger a specific one. |
is this new behaviour? (so I learn something every day  )
I found it in the documentation (If you do not specify a channel name, the channel initiator searches the channel definition files until it finds a channel that is associated with the named transmission queue.),
but when I try it on an 6.0.0.0 system it doesn't work 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Apr 05, 2007 4:00 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
hmmm, it's also in the MQ 5.3 Intercommunication Guide,
I never noticed it...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 05, 2007 5:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Michael Dag wrote: |
| fjb_saper wrote: |
| You only need to specify the channel name if you have multiple channels sharing the same XMITQ and you want to trigger a specific one. |
is this new behaviour? (so I learn something every day )
I found it in the documentation (If you do not specify a channel name, the channel initiator searches the channel definition files until it finds a channel that is associated with the named transmission queue.),
but when I try it on an 6.0.0.0 system it doesn't work |
6.0.0.0 is not a good release. You should be at 6.0.2.0 or better at 6.0.2.1
The first "stable" release in 6.0, I consider to be 6.0.1.1
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Apr 05, 2007 10:37 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I tried it on MQ V5.3 and it works as described.
I will still continue to use the channelname in the TRIGDATA as a best practice, because I can see many eyebrowes lifting in the admin department... 
on V6 you can use: dis chl(*) where(XMITQ EQ QMgrName) all
to find the channel for a specific Transmission Queue, but that does not
work for < V6.0
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Drax |
| Posted: Tue Apr 24, 2007 9:42 pm Post subject: |
|
|
Novice
Joined: 16 Apr 2007
Posts: 12
Location: China
|
I met the same problem on AIX platform, in the MQ ver 5.2, dont specify the userdata is ok, but in the MQ ver 6, when I dont specify the userdata, the chl will not start when put a message in the xmitq,if I specify the userdata, all things are fine, could someone tell me why?
 |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Tue Apr 24, 2007 9:51 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
more info would be needed, but first I would look whether you have more then 1 channel with the same xmitq
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Drax |
| Posted: Tue Apr 24, 2007 11:32 pm Post subject: |
|
|
Novice
Joined: 16 Apr 2007
Posts: 12
Location: China
|
there is only one chl for the xmitq I think :
dis chl(*) where(xmitq eq mqm2)
4 : dis chl(*) where(xmitq eq mqm2)
AMQ8414: Display Channel details.
CHANNEL(MQNUS029T01.MQM2.T01) CHLTYPE(SDR)
XMITQ(MQM2)
in the process if I dont specify the userdata the msg will held in the xmitq and if I specify the chl name in the userdata, then the chl started,I dont know why, and there is another server used the MQ ver 5.2 if the userdata in the process is not specified, the chl will auto start when there is msg coming into the queue as well, I dont know if the mq version make it different |
|
| Back to top |
|
|
| Nigelg |
| Posted: Wed Apr 25, 2007 12:49 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
There was a bug in 6.0.0.0 which caused a triggered channel without TRIGDATA to fail to start. This is fixed in 6.0.1.0 in APAR IY77282, defect 95814.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
| Drax |
| Posted: Wed Apr 25, 2007 1:12 am Post subject: |
|
|
Novice
Joined: 16 Apr 2007
Posts: 12
Location: China
|
|
| Back to top |
|
|
| Drax |
| Posted: Wed Apr 25, 2007 6:14 pm Post subject: |
|
|
Novice
Joined: 16 Apr 2007
Posts: 12
Location: China
|
| Hi, are there someone have experience about installing the fixpack for MQ, please give me some advise about the fixpack installing,thx |
|
| Back to top |
|
|
| Carl Bloy |
| Posted: Fri Aug 03, 2007 1:56 am Post subject: I think the problem still exists? |
|
|
Acolyte
Joined: 16 Dec 2003
Posts: 69
Location: England
|
All, we have the channel triggering problem with the following version on AIX 5.3
mqm@d63n03:/home/mqm $ dspmqver
Name: WebSphere MQ
Version: 6.0.2.1
CMVC level: p600-201-070307
BuildType: IKAP - (Production)
Messages arrive on the XMTIQ and channel doens't get triggered? I can manually start the channel all runs ok. After finding this post I set the trigger data to the name of the channel and hey presto channel triggered ok! I think I need to raise this with IBM.
_________________
Regards
Carl |
|
| Back to top |
|
|
|
|
