Channel Triggers 1

[kulpreet]

I'm trying channel triggers and have the following config on my machine as per the ibm PDF's but it is not working.
Can you tell me where I am going wrong?

First Queue Manager
QM MGR1
XMITQ MGR2
Usage : Transmission
Triggering : ON
Trigger Type: Depth
Message Priority : 0
Initiation Queue Name : INITQ
Process Def. Name : TEST
Initiation Queue INITQ
Usage : Normal
Process Process Def. Name : TEST
Appication Type : Windows NT
User Data: MGR1.TO.MGR2

Remote Def. to.MGR2 (RemoteQ :to.MGR1, RemoteQM : MGR2, XMITQ : MGR2)
Sender Ch. MGR1.TO.MGR2 (Conn. name : IPAddr +Port no. of MGR2) (XMITQ : MGR2)

Channel Initiator Name of initaition Q: INITQ
Status : Running

Second Queue Manager
QM MGR2
LCLQ from.MGR1
Receiver Ch. MGR1.TO.MGR2
Listener Running at this end at the correct port no.

The above configuration is working fine if the channels are already running.
Now, I'm trying channel triggers and have stopped both the sender and receiver channels so that i can trigger these. But triggering is not working here and the messages keep lying in the XMITQ.
Please guide as to what mistake i might be making....

Thanks in advance

kulpreet

 

[smeridew]

I've seen this before. If you manually STOP the channels, they will not trigger. Set the disconnect interval to a fairly low number, like 30 seconds. Let the channel go into an 'inactive' state, and then put your messages onto the transmission queue. You'' see the channel start up just fine.

By the way, you don't need to create a process definition to trigger a channel. The Channel initiator will start the channel for you. All you need to do is specify the name of the Channel in the 'trigger data' parameter of the transmission queue. Also, specify SYSTEM.CHANNEL.INITQ in the InitQ parameter. (If you want to use another initq, you have to create another channel initiator using MQ Services, and specify the name of your initq).

Cheers,

Scott Meridew
MQ Squared Inc.

http://www.mqsquared.com