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 » IBM MQ API Support » Problems in Trigger Monitor on Windows Client

Post new topic  Reply to topic Goto page 1, 2  Next
 Problems in Trigger Monitor on Windows Client « View previous topic :: View next topic » 
Author Message
Sanjeev
PostPosted: Tue Sep 27, 2005 10:25 pm    Post subject: Problems in Trigger Monitor on Windows Client Reply with quote

Novice

Joined: 27 Sep 2005
Posts: 15

Hi,

I am trying to execute a Trigger Monitor 'runmqtmc' (command line) on my Client Machine(Windows) to access the Local Queue on the OS/2 Server...
This trigger monitor tries to execute a DotNet(.exe) app as the background process and consumes the Messages from the Local queue...
But the DotNet(.exe) app is not getting fired and the messages from the queue are not being consumed...
The output on the command window is as follows:

"Waiting for a trigger message
Not a valid trigger message....."


Pleae post with necessary solution remedies.....
Back to top
View user's profile Send private message
wschutz
PostPosted: Wed Sep 28, 2005 1:59 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

OS/2 huh? I didn't think that was still supported, oh well...
Quote:
"Waiting for a trigger message
Not a valid trigger message....."

Are you sure the triggering monitor is monitoring an INITIATION QUEUE and
not your application queue? Can you show use the command line from runmqtmc and the relevant queue and process definitions on the OS/2 qmgr?
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
hopsala
PostPosted: Wed Sep 28, 2005 2:05 am    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

Hi Sanjeev, my guess is that your not setting up the trigger properly, and probably ran runmqtrm against the application queue instead of the initiation queue.

Anyway, use the "Search" button on this forum with the string "Not a valid trigger message" and "search for all items", I found many posts about this topic which will probably help you; it is always a good idea to search before posting. When I searched, I found:
Getting "Not a Valid trigger message" (a description of a similar problem to yours)
Triggering is not taking the text message (another similar prob)
Triggering applications running on MQ Client (a discussion about triggering)

Next time, I won't search for you . If you still have problems, post us your queue and initq settings, and the runmqtrm command you issued; if you solved your problem, please post how you did it for future generations.
Back to top
View user's profile Send private message
Sanjeev
PostPosted: Wed Sep 28, 2005 2:11 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2005
Posts: 15

Hi,
Below are the Trigger Message Details created at OS/2 Server:

------------------------------------------------------------------------------
Queue name . . . . . . . . : UKG.BGN.CICSB33.PQ0136.LOCAL
Disposition . . . . . . . . : QMGR MYT1

Trigger Definition

Trigger type . . . . . . : F F=First, E=Every, D=Depth, N=
Trigger set . . . . . . : Y Y=Yes, N=No

Trigger message priority : 0 0 - 9
Trigger depth . . . . . : 1 1 - 999999999

Initiation queue . . . . : UKG.BGN.CICSB33.PQ0136.TRIGGER
Process name . . . . . . : UKGBGN.PQ0136
Trigger data . . . . . . :
------------------------------------------------------------------------------
Process name . . . . . . . . UKGBGN.PQ0136
Disposition . . . . . . . . : QMGR MYT1
Description . . . . . . . . : UKG GBN process on Win

Application type . . . . . : WINDOWS

Application
ID . . . : C:\MQCogen\bin\Release\MQCogen.exe
------------------------------------------------------------------------------


Thus the trigger monitor must 'listen' to queue UKG.BGN.CICSB33.PQ0136.TRIGGER.

and the command line command is as follows:

C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.LOCAL

Please check up!!!!
Back to top
View user's profile Send private message
wschutz
PostPosted: Wed Sep 28, 2005 2:25 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

Quote:
Thus the trigger monitor must 'listen' to queue UKG.BGN.CICSB33.PQ0136.TRIGGER.

and the command line command is as follows:

C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.LOCAL

shouldn't it be:

Code:
C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.TRIGGER
?
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
hopsala
PostPosted: Wed Sep 28, 2005 2:31 am    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

Sanjeev wrote:
C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.LOCAL

Obviously, you got lazy and did not read the posts I gave you to read, or did not read them carefully enough; otherwise you would've found the answer to your question.

See what schutz wrote, there's your answer. Next time, please take note to the posts people gave you, almost every known question to man concerning wmq has been answered here at one time or another, and it is essential to the health of this forum that you take the time to make your own research.
Back to top
View user's profile Send private message
Sanjeev
PostPosted: Wed Sep 28, 2005 2:39 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2005
Posts: 15

Uhhhhhhhhhhh!!!
For your kind information i tried with both the commands

C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.LOCAL

and

C:\Program Files\IBM\WebSphere MQ\bin\runmqtmc -m MYT1 -q UKG.BGN.CICSB33.PQ0136.TRIGGER

and for both i am getting same type of error message...

My queries are like am i missing anything from my side in the part of executing the commands or is there something that need to adjusted from the QMGR side???
Back to top
View user's profile Send private message
wschutz
PostPosted: Wed Sep 28, 2005 2:48 am    Post subject: Reply with quote

Jedi Knight

Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)

Are there any messages on the dead letter queue? (If you don't have a dead letter queue defined, then alter the qmgr to define SYSTEM.DEAD.LETTER.QUEUE as the dead letter queue). i believe that the trigger mnitor should put the offending message there. use amqsbcg to view it if you find it.
_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
hopsala
PostPosted: Wed Sep 28, 2005 2:53 am    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

Ok, first you need to know that the trigger monitor should run on the TRIGGER queue, this is a queue to which the trigger messages are sent. Second, the LOCAL queue should be the queue to which you are sending the message. Thus, you put a msg to LOCAL, a trigger is formed in TRIGGER and your trigger monitor should read it.

Did you try triggering a local application? Possibly you have some conversion problem on your hands.

Now, keep in mind this is *not* an online support forum, try things yourself! Be creative! Go wild! no way that in the 5 minutes between my posts and schutzs, you had the chance to make any independant research. The only way to learn mq is to deal with it yourself - listen to our advice, take the time to think about it, try this, try that, if two hours later still no luck, post again.
Back to top
View user's profile Send private message
Sanjeev
PostPosted: Wed Sep 28, 2005 3:44 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2005
Posts: 15

For checking with the Dead Queues i don't have an option since the concerned person for handling the QMGR is located as Swiss...

So any other suggestions or advices, meanwhile i am trying from my side with other possibilities....
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Sep 28, 2005 4:05 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

So, your trigger monitor starts successfully. And when it's running, you can see an Open Input Count on the TRIGGER Queue.

Then your application places a message on the LOCAL queue, and you get an error from the trigger monitor that says it did not receive a valid trigger message?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
hopsala
PostPosted: Wed Sep 28, 2005 4:08 am    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

Sanjeev wrote:
For checking with the Dead Queues i don't have an option since the concerned person for handling the QMGR is located as Swiss...

Use amqsbcgc, the client equivalent to amqsbcg... (most samples have a client equiv).
Back to top
View user's profile Send private message
Sanjeev
PostPosted: Wed Sep 28, 2005 4:26 am    Post subject: Reply with quote

Novice

Joined: 27 Sep 2005
Posts: 15

Yes i tried to use amqsbcgc and able to view the messages when i try to load sample messages into the TRIGGER queue using the PQEdit tool..

but i don't understand how this is helpful in the debugging the solution...
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Wed Sep 28, 2005 4:30 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Sanjeev wrote:
Yes i tried to use amqsbcgc and able to view the messages when i try to load sample messages into the TRIGGER queue using the PQEdit tool..


DON'T DO THAT!

The only thing that should write to the queue you have named UKG.BGN.CICSB33.PQ0136.TRIGGER is the queue manager.

You should only ever put messages on UKG.BGN.CICSB33.PQ0136.LOCAL.

Sanjeev wrote:
but i don't understand how this is helpful in the debugging the solution...

It is helpful because every message on the DLQ has a Reason Code in the MQDLH that tells you WHY it ended up on the DLQ.

But in your case, the problem is simply that you are trying to write data messages to the initiation queue.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
hopsala
PostPosted: Wed Sep 28, 2005 4:38 am    Post subject: Reply with quote

Guardian

Joined: 24 Sep 2004
Posts: 960

Sanjeev wrote:
Yes i tried to use amqsbcgc and able to view the messages when i try to load sample messages into the TRIGGER queue using the PQEdit tool..

Wait, I hope you're not just loading any messages to TRIGGER queue; this queue should only contain trigger messages which are automatically created by the qm, you shouldn't put messages directly to this queue otherwise you'll get "invalid trigger message". To re-emphesize what I said - you put a msg to LOCAL and the qm automatically generates a msg to TRIGGER q, you *do not* put to the TRIGGER q yourself.
I think you're still confused as to how triggering works, read the posts I sent you and re-read the application programming guide.

Sanjeev wrote:
but i don't understand how this is helpful in the debugging the solution...

Just to be clear, I meant use the amqsbcgc to look at (possibly) the trigger msgs put to the dead letter queue. If you can indeed find them, try undesrtanding why their structure is off, it should be a normal trigger structure MQTMC2 which looks something like this:
Quote:
1 QName
2 ProcessName
3 TriggerData
4 ApplType
5 UserData
6 QMgrName

(full description and field lengths can be found in Application programming reference on the MQTMC2 chapter)
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » IBM MQ API Support » Problems in Trigger Monitor on Windows Client
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.