|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Triggering a channel |
« View previous topic :: View next topic » |
Author |
Message
|
jainvik7 |
Posted: Fri Feb 24, 2006 5:21 am Post subject: Triggering a channel |
|
|
Apprentice
Joined: 19 Feb 2006 Posts: 38
|
Hi,
I have 2 queue managers QM1 and QM2. I have a XMITQ QM2 on QM1 and has the following settings--
DESCR( ) PROCESS( )
BOQNAME( ) INITQ(SYSTEM.CHANNEL.INITQ)
TRIGDATA(QM1.TO.QM2) CLUSTER( )
CLUSNL( ) QUEUE(QM2)
CRDATE(2006-02-19) CRTIME(18.59.11)
ALTDATE(2006-02-24) ALTTIME(07.12.00)
GET(DISABLED) PUT(ENABLED)
DEFPRTY(0) DEFPSIST(NO)
MAXDEPTH(5000) MAXMSGL(4194304)
BOTHRESH(0) SHARE
DEFSOPT(SHARED) HARDENBO
MSGDLVSQ(PRIORITY) RETINTVL(999999999)
USAGE(XMITQ) TRIGGER
TRIGTYPE(FIRST) TRIGDPTH(1)
TRIGMPRI(0) QDEPTHHI(80)
QDEPTHLO(20) QDPMAXEV(ENABLED)
QDPHIEV(DISABLED) QDPLOEV(DISABLED)
QSVCINT(999999999) QSVCIEV(NONE)
DISTL(YES) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(OPEN) IPPROCS(0)
OPPROCS(0) CURDEPTH()
As you would have noticed, I am trying to trigger the channel (QM1.To.QM2) when a messages of priority 0 arrives on the Xmitq. The channel is currently in the stopped state. However, when I send a message from QM1 to QM2 , the channel does not seem to start.
Can somebody please help me or let me know if I am missing out something. All the settings on the sending and receiving side is fine (I have tested that). I am using MQ series 5.3 on windows 2000.
Thanks |
|
Back to top |
|
 |
jainvik7 |
Posted: Fri Feb 24, 2006 5:27 am Post subject: |
|
|
Apprentice
Joined: 19 Feb 2006 Posts: 38
|
It seems to work if the current status of the sender channel QM1.TO.QM2 is set to "inacitve" rather than setting it to "stopped".
Can somebody please let me know the exact reasons or some pointers for this ?
Thanks |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Feb 24, 2006 5:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
That's the way this works.
A channel that is "STOPPED" is exactly that. Stopped until manually started.
If you want to trigger channels, then don't try and control them at all. When the qmgr starts up, they will initialize in the "inactive" state (unless there are messages waiting to be moved, then they will be triggered and run). When messages need to get moved, the channel will start, run until all messages have been moved and then for a bit longer, and then return to the inactive state.
The Intercommunications manual has all the gory details, conveniently located at your friendly neighborhood InfoCenter http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
jainvik7 |
Posted: Fri Feb 24, 2006 5:34 am Post subject: |
|
|
Apprentice
Joined: 19 Feb 2006 Posts: 38
|
Thanks Jeff for your reply.
 |
|
Back to top |
|
 |
HubertKleinmanns |
Posted: Mon Feb 27, 2006 5:09 am Post subject: |
|
|
 Shaman
Joined: 24 Feb 2004 Posts: 732 Location: Germany
|
jainvik7 wrote: |
It seems to work if the current status of the sender channel QM1.TO.QM2 is set to "inacitve" rather than setting it to "stopped".
Can somebody please let me know the exact reasons or some pointers for this ?
Thanks |
A channel goes into state STOPPED, when it is stopped manually (by issuing the command STOP CHANNEL(...) or when the RETRY count has been reached. _________________ Regards
Hubert |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|