| Author |
Message
|
| Sanjeev |
 Posted: Thu Sep 29, 2005 10:26 pm Post subject: |
 |
|
Novice
Joined: 27 Sep 2005
Posts: 15
|
Finally for more confirmation on this MQSeries work,
What should be the Client Trigger Monitor Command...
The command that i am working with is like this:
runmqtmc -m QmgrName -q Queue.LOCAL
and itz displaying the "Not a valid trigger message....."
Please correct me if i have entered anything wrong in processing the commands.... |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Sep 29, 2005 11:26 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| runmqtmc -m QmgrName -q Queue.LOCAL |
I hope the LOCAL at the end of that doesn't mean you are still trying to use: UKG.BGN.CICSB33.PQ0136.LOCAL In all the posts so far, you have been told that the queue you need to start the Trigger monitor on is: UKG.BGN.CICSB33.PQ0136.TRIGGER
OK, so describe exactly what you are doing, step by step. Explain everything in detail. If you issue a command, give us that command in full. If you run an application that PUTs a message, tell us where that message is PUT.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| hopsala |
| Posted: Fri Sep 30, 2005 4:13 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| Sanjeev wrote: |
| runmqtmc -m QmgrName -q Queue.LOCAL |
What is becoming increasingly apparent, is that you have one problem and one problem only: you're not reading what we told you; I don't mean to be snide, but that's the way it is.
| wschutz wrote: |
| Are you sure the triggering monitor is monitoring an INITIATION QUEUE and not your application queue? |
| hopsala wrote: |
| and probably ran runmqtrm against the application queue instead of the initiation queue. |
| hopsala wrote: |
| Ok, first you need to know that the trigger monitor should run on the TRIGGER queue |
| wschutz wrote: |
| C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.TRIGGER |
| jefflowrey wrote: |
| The only thing that should write to the queue you have named UKG.BGN.CICSB33.PQ0136.TRIGGER is the queue manager. |
Go back to the beginning of this post, and start reading, slowly and carefully, every single thing we told you, then implement it - it's all true; we have repeatedly told you the same thing again and again, but it seems we are ignored. I draw my hands from this thread.
(Concerning the Let's not be condescending in our responses I find this to be a justified case.) |
|
| Back to top |
|
|
| Sanjeev |
| Posted: Sun Oct 09, 2005 9:01 pm Post subject: |
|
|
Novice
Joined: 27 Sep 2005
Posts: 15
|
Now for all good news that i am able to consume the messages thru the trigger monitor...by executing the runmqtmc command...
Now please advice me for combining these commands into a group of commands like the Batch file or the appropriate ways so that they can be executed at one go...this should be feasible even if the system is shut down and the queue should be triggered automatically using the trigger monitor (runmqtmc) command..... |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Oct 10, 2005 2:28 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| Now for all good news that i am able to consume the messages thru the trigger monitor...by executing the runmqtmc command... |
Thats good news ....
| Quote: |
| Now please advice me for combining these commands into a group of commands like the Batch file or the appropriate ways so that they can be executed at one go...this should be feasible even if the system is shut down and the queue should be triggered automatically using the trigger monitor (runmqtmc) command..... |
Are you looking for a script file to automatically startup the trigger monitor at system restart? If memory serves, you need the trigger monitor to run on Windows. Have a look at supportpac MA7K here:
http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg24000149&loc=en_US&cs=utf-8&lang=en
Or, there are ways to make a program into a windows service so that you can have runmqtmc automatically start at system setup (but, of course, if the queue manager goes down, then runmqtmc dies and doesn't automatically try to reconnect).
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 10, 2005 3:32 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Scheduled Tasks is a very simple way to turn a program or a batch file into a windows background process.
The Windows support pack Wayne mentions is excellent as well.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Sanjeev |
| Posted: Tue Oct 11, 2005 3:19 am Post subject: |
|
|
Novice
Joined: 27 Sep 2005
Posts: 15
|
Thanks for the Link it helped me a lot for installing the Service and run when the messages arrive...
But when i sent the setup to the Onsite peopel they are facing some problems like this:
"User exit not valid....
Channel program 'MYL1.CLIENT' ended because user exit 'XT426' is not valid.
Ensure that the user exit is specified correctly in the channel definition, and that the user exit program is correct and available..."
Please advice...... |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Oct 11, 2005 3:29 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Do you really need to be told what the problem is now?
It looks rather obvious from the error msg.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
