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 IndexGeneral IBM MQ Supportproblem with triggering

Post new topicReply to topic Goto page Previous  1, 2
problem with triggering View previous topic :: View next topic
Author Message
sebastianhirt
PostPosted: Wed Jul 27, 2005 8:00 am Post subject: Reply with quote

Yatiri

Joined: 07 Jun 2004
Posts: 620
Location: Germany

csaunders wrote:
can someone give me background on what the channel initator is, and how I create one?


The Channel initiator is more or less the same as a trigger monitor. The only difference is that it starts a channel rather then an application.

If you tell us your OS, somebody will post you the appropriate command line
Back to top
View user's profile Send private message
csaunders
PostPosted: Wed Jul 27, 2005 8:44 am Post subject: Reply with quote

Acolyte

Joined: 27 Mar 2003
Posts: 64
Location: Arlington, Va

ps -ef|grep mqchi
mqm 4765 4760 0 11:59:32 pts/9 0:00 grep mqchi
mqm 13016 13010 0 Jul 12 ? 0:00 /opt/mqm/bin/runmqchi -m USVI_APP1A

ok, well i stopped/started the qmnanager, I put a test message on the q, i also made sure the channel was inactive, it was, the channel started and the message got sent, i think stopping and starting the qmanager did the trick
Back to top
View user's profile Send private message AIM Address
wschutz
PostPosted: Wed Jul 27, 2005 11:01 am Post subject: Reply with quote

Jedi Knight

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

Quote:
But if you want to be 100% sure, then type in on Unix/Linux

ps -ef|grep mqchi

on Windows
open the MQServices Snap in and click to your queue manager name and see there
or
Code:
dis qstatus(system.channel.initq) type(handle)

_________________
-wayne
Back to top
View user's profile Send private message Send e-mail AIM Address
csaunders
PostPosted: Thu Jul 28, 2005 6:16 am Post subject: Reply with quote

Acolyte

Joined: 27 Mar 2003
Posts: 64
Location: Arlington, Va

still istn working, anyone have a cron script that is usefull for this...
Back to top
View user's profile Send private message AIM Address
jefflowrey
PostPosted: Thu Jul 28, 2005 6:20 am Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

csaunders wrote:
still istn working, anyone have a cron script that is usefull for this...


What happens if you disable and then reenable triggering on the xmitq?

Are there any errors in the logs? Any FDCs?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
csaunders
PostPosted: Thu Jul 28, 2005 6:56 am Post subject: Reply with quote

Acolyte

Joined: 27 Mar 2003
Posts: 64
Location: Arlington, Va

worth a shot, let me try
Back to top
View user's profile Send private message AIM Address
csaunders
PostPosted: Thu Jul 28, 2005 7:07 am Post subject: Reply with quote

Acolyte

Joined: 27 Mar 2003
Posts: 64
Location: Arlington, Va

jefflowrey wrote:
csaunders wrote:
still istn working, anyone have a cron script that is usefull for this...


What happens if you disable and then reenable triggering on the xmitq?

Are there any errors in the logs? Any FDCs?
AH HA, nice! that seemend to work!!! I had 130 messages on my xmitq then I turnend off triggering, then back on, and viloa, messages sent!!
Back to top
View user's profile Send private message AIM Address
jefflowrey
PostPosted: Thu Jul 28, 2005 7:39 am Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

csaunders wrote:
AH HA, nice! that seemend to work!!! I had 130 messages on my xmitq then I turnend off triggering, then back on, and viloa, messages sent!!


Yeah, this is a standard technique for retriggering. It doesn't solve your problem, but it's very easy to cron a suitable runmqsc - so it "fixes" your problem.

The question remains of why the channel isn't triggering in the first place.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
kevinf2349
PostPosted: Thu Jul 28, 2005 8:26 am Post subject: Reply with quote

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

When triggering isn't working....what is the status of the channel?

Make sure it is 'INACTIVE' and not 'STOPPED'.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Thu Jul 28, 2005 8:31 am Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7723

You don't have some other process holding the XMITQ open for browsing do you?

If you do, MQ will see that the queue is open by something (it does not care that it is not the channel), and will not bother triggering.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
sebastia
PostPosted: Fri Aug 05, 2005 2:30 am Post subject: Reply with quote

Grand Master

Joined: 07 Oct 2004
Posts: 1003

does the channel have "DISCINT” set to “0” ?????????????
it helps a lot ..... )
.
Back to top
View user's profile Send private message Visit poster's website
kevinf2349
PostPosted: Fri Aug 05, 2005 7:42 pm Post subject: Reply with quote

Grand Master

Joined: 28 Feb 2003
Posts: 1311
Location: USA

Quote:
does the channel have "DISCINT” set to “0” ?????????????
it helps a lot ..... )
.


Helps how? The only thing setting DISICINT to 0 does is prevent a channel from being disconnected due to inactivity.... probably the worst thing you could do to a triggered channel...unless you only want triggering to be used purely for initial channel start up....and I would contend that a starttup script was less trouble to set up in that circumstance.

Setting DISCINT to 0, in my opinion, effectively negates the main purpose for triggering channels.
Back to top
View user's profile Send private message
LearnMQSI
PostPosted: Sat Aug 06, 2005 5:08 pm Post subject: RE: problem with triggering Reply with quote

Centurion

Joined: 20 Aug 2002
Posts: 137

First of all, You don't need to have all this TRIGGER, TRIGDATA, TRIGTYPE(FIRST) in your transmission queue. You should be doing this in your local queue. Your channel would call your transmission queue, so have your transmission queue with simple USAGE(XMITQ) attribute setup.

LearnMQSI
_________________
IBM Certified System Administrator - WebSphere MQ 5.3
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Aug 06, 2005 8:04 pm Post subject: Re: RE: problem with triggering Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20763
Location: LI,NY

LearnMQSI wrote:
First of all, You don't need to have all this TRIGGER, TRIGDATA, TRIGTYPE(FIRST) in your transmission queue. You should be doing this in your local queue. Your channel would call your transmission queue, so have your transmission queue with simple USAGE(XMITQ) attribute setup.

LearnMQSI


For channel triggering you want your xmitq to have following attributes:

TRIGGER, TRIGTYPE(FIRST) INITQ(SYSTEM.CHANNEL.INITQ) USAGE(XMITQ)

in fact you need the initq to be the one you defined for the channel initiator...

Back to top
View user's profile Send private message Send e-mail
Display posts from previous:
Post new topicReply to topic Goto page Previous  1, 2 Page 2 of 2

MQSeries.net Forum IndexGeneral IBM MQ Supportproblem with triggering
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.