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 Installation/Configuration Support » why can't I see the trigger messages ?

Post new topic  Reply to topic Goto page Previous  1, 2, 3
 why can't I see the trigger messages ? « View previous topic :: View next topic » 
Author Message
exerk
PostPosted: Thu Jan 15, 2009 2:49 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

mqjeff wrote:
Actually, I got that wrong.

I meant to imply that you were Vitor's Igor these days, as a response to his claims that he was no longer mine.


A title that I am much more than happy to claim . I am having some additional fingers stitched on next week!
_________________
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
View user's profile Send private message
sebastia
PostPosted: Thu Jan 15, 2009 3:09 pm    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

Jeff - I have tried your sugestion :
"just use something like amqsbcg or rfhutil as a trigger monitor"

But, unfortunatelly, it does not work

IPPROCS
The number of handles that are currently open for input for the queue (either input-shared or input-exclusive).
This does not include handles that are open for browse.

With AMQSBCG, the IPPROCS count stayed at 0,
while AMQSGET did set it to one.

RFHUTIL was quite worse, as "Browse" does not have any timeout ...
neither "Read" ...

So .. I am still investigating how to "catch" a Trig msg in Init que !

Guess this is my spirit today ..
Back to top
View user's profile Send private message Visit poster's website
Vitor
PostPosted: Thu Jan 15, 2009 3:19 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

sebastia wrote:
So .. I am still investigating how to "catch" a Trig msg in Init que !

Guess this is my spirit today ..


Your spirit appears to be ignoring my suggestion about the trigger monitor. Part of the whole "crawling on broken glass as a survival strategy" I imagine.

I'm sure this self-imposed suffering improves your spirit, and makes you a better person. Whilst also being a valuable learning experience.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sebastia
PostPosted: Thu Jan 15, 2009 3:25 pm    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

Vitor : I agree the IBM's trigger monitor is good enough,
and I shall use it forever, as far as I know.

I want to catch a trigger message, and I did just right now :

If you launch RFHUTIL pointing to a queue manager,
and you read once a queue, the queue remains "open" to rfhutil :

====================================
1 : display qstatus(INITQ) all

AMQ8450: Display queue status details.
QUEUE(INITQ) TYPE(QUEUE)
CURDEPTH(0) IPPROCS(1)
...

2 : display qstatus(INITQ) type(handle)

AMQ8450: Display queue status details.
QUEUE(INITQ) TYPE(HANDLE)
APPLTAG(C:\sebas\Eines\rfhutilc.exe) APPLTYPE(USER)
====================================
Now, you can send a msg using AMQSPUT,
and using RFHUTIL's Browse you DO catch de Trigger message.

It is not self-punishment, neither suffering - I just dont like
not to be able to do some things I think I can do ..

( maybe this is another's person hell, who knows )

()
Back to top
View user's profile Send private message Visit poster's website
Vitor
PostPosted: Thu Jan 15, 2009 3:26 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

exerk wrote:
A title that I am much more than happy to claim


Velcome to the lab! Slip into this white coat, lurch over to that switch and wait for my signal......
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sebastia
PostPosted: Thu Jan 15, 2009 3:34 pm    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

And the final conclusion : MIRRORQ is not valid
to duplicate Trigger messages.

a) usign AMQSPUT, the msg in INITQ is copied (by MIRRORQ)
into INITQ_COPY

b) if I have a Trigger monitor on INITQ, it is fired,
but INITQ_COPY has nothing

Well, will have to live without this tool ...

()
Back to top
View user's profile Send private message Visit poster's website
exerk
PostPosted: Thu Jan 15, 2009 3:48 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Vitor wrote:
exerk wrote:
A title that I am much more than happy to claim


Velcome to the lab! Slip into this white coat, lurch over to that switch and wait for my signal......


Yeth mathter...
_________________
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
View user's profile Send private message
bruce2359
PostPosted: Thu Jan 15, 2009 5:27 pm    Post subject: Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9475
Location: US: west coast, almost. Otherwise, enroute.

I'm struggling to come up with something intellegent-sounding to add to this post...

Trigger messages are merely event messages. I tend to agree that there is little/no value in saving event messages, be they trigger, channel or admin event messages. This seems to me like saving old calendars.

When properly configured and left untouched (trigger monitor, queue definitions, process definitions, application programs), triggering works. Change one of these, and there is potential for triggers to fail.

Event monitoring software would be an approach to detecting failed triggers in real time - that and end-users complaining.

Unprocessed trigger messages or unprocessed application messages because of failed triggers should provide sufficient information to begin the diagnostic process.
_________________
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
View user's profile Send private message
Vitor
PostPosted: Fri Jan 16, 2009 12:49 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

bruce2359 wrote:
I'm struggling to come up with something intellegent-sounding to add to this post...


What, like the B-movie monster posts???!!!!???

I agree with your points, but sebastia seems set upon his course for his own reasons and I think we need to respect that, if not agree with it.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Jan 16, 2009 12:52 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

sebastia wrote:
And the final conclusion : MIRRORQ is not valid
to duplicate Trigger messages.
...
Well, will have to live without this tool ...

()


One final correction if I may:

The mirrorq exit is a sample, not a tool, not considered production strength and not intended to be used unmodified. If it's not doing what you want/need, change it and ride into the sunset.

(Monster movie to western in a single thread. Gosh.)
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sebastia
PostPosted: Fri Jan 16, 2009 5:14 am    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

Vitor - thanks for your respect !

1) And I have come to another situation where it is nice
to be able to "display" a trugger message :
when teaching someone MQ.
You talk about data q, init q, trigger message and a trigger monitor.
A student raises his hand and says : can I see one ?
You have to be able to show it, should'nt you ?

2) "tool" - it was a tool to me, not for everybody.
Neither for production, just to tune the development envir and apps.

Cheers.
Back to top
View user's profile Send private message Visit poster's website
Vitor
PostPosted: Fri Jan 16, 2009 5:28 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

sebastia wrote:
You have to be able to show it, should'nt you ?


Yes, and I would do (and have done) using my suggested method. If I had £10 for each time in the last 11 years I'd been told a triggered app wasn't starting because no trigger was being raised I'd retire to Tahti on the proceeds! First step is to make sure a) the trigger message is coming out & b) contains the right EnvData & UserData, exactly as you are doing.

sebastia wrote:
2) "tool" - it was a tool to me, not for everybody.
Neither for production, just to tune the development envir and apps.


My correction was not aimed at you specifically, but a general correction for the benefit of future readers who might believe (or have their existing belief confirmed) that mirrorq is a tool a la support pac & they can just ram it into the queue manager and walk away.

My standard rant on the dangers of exits should be inserted here.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Fri Jan 16, 2009 5:32 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Vitor wrote:
If I had £10 for each time in the last 11 years I'd been told a triggered app wasn't starting because no trigger was being raised I'd retire to Tahti on the proceeds!


Of course, £1 for each time I'd been told "MQ's lost my message" and I'd be able to buy Tahti!
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sebastia
PostPosted: Fri Jan 16, 2009 5:36 am    Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

Just to finish this thread ...

... your "suggested method" is running RUNMQTRM in foreground ...

... or RFHUTIL pointing to INITQ

... am I right ?

About your "£" ... I agree 100%.

And I am sure you (and your back) deserve 40 days in Tahiti ...
Back to top
View user's profile Send private message Visit poster's website
Vitor
PostPosted: Fri Jan 16, 2009 5:41 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

sebastia wrote:
... your "suggested method" is running RUNMQTRM in foreground ...


Yes. Simple, efficient and a wealth of diagnostic options.

sebastia wrote:
And I am sure you (and your back) deserve 40 days in Tahiti ...


When I go, it will be forever.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3 Page 3 of 3

MQSeries.net Forum Index » IBM MQ Installation/Configuration Support » why can't I see the trigger messages ?
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.