| Author |
Message
|
| sprakashit |
 Posted: Sat Oct 15, 2005 12:26 am Post subject: Why Sender channel has to be started manually in iSeries |
 |
|
Newbie
Joined: 13 Jul 2005
Posts: 6
|
Hi ,
After channel initiator is started using STRMQMCHLI in iSeries, why the Sender Channel has to be started manually using STRMQMCHL.
Will the Channel Initiator itself won't start the Sender Channel automatically when first trigger message arrives.
I did the same configuration in windows XP, Channel intiator automatically starts the channel after the receipt of the first trigger message. But, I am not sure why it is not happening in iSeries.
Regards,
Prakash |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Sat Oct 15, 2005 2:17 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
What version of MQ / CSD?
What configuration of queues / channels / channel initiator?
without additional info, help becomes a guessing game...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| sprakashit |
| Posted: Tue Oct 18, 2005 4:09 am Post subject: Re:Why Sender channel has to be started manually in iSeries |
|
|
Newbie
Joined: 13 Jul 2005
Posts: 6
|
Hi,
In my iSeries box , MQVersion is 5.2 and it is at CSD level 6.
Let me rephrase problem which I am facing,
Inorder to send messages to a remote queue, I created a remote queue definition
'A' with Transmission Queue as 'X'.
The following setups where already there in the system
- Transmission Queue is trigger enabled with
trigger type - *ALL,
trigger data - sender channel name - C ,
Initiation queue -'I' and
process 'P'.
- Process 'P' is created with
Application identifier: AMQRMCLA [MCA name]
User data: - Sender Channel name - C
So, whenever a message comes into queue 'A', a trigger message will be sent to initation queue - 'I'. Inorder to monitor this initiation queue, I started channel initiator using STRMQMCHLI command. So, I expected channel initiator should start the corresponding sender channel whenever a first trigger message arrives. Since it is not happening, I have to start the sender channel as well by using STRMQMCHL command after starting the channel initiator.
I have a doubt that, why Sender channel is not started automatically when first trigger message arrives at channel initiation queue ?
Regards,
Prakash |
|
| Back to top |
|
|
| nathanw |
| Posted: Tue Oct 18, 2005 4:18 am Post subject: |
|
|
Knight
Joined: 14 Jul 2004
Posts: 550
|
out of curiosity, once it is running does it stay running ie even if the channel is inactive and data ispassed does it start up and start passing messages?
reason I ask is that sometimes a manually shutdown requires a manual startup
had this problem previously whereby the box was backed up over night and rebboted which meant that a startup script was required to initiate the channels and start them manually. |
|
| Back to top |
|
|
| sprakashit |
| Posted: Tue Oct 18, 2005 4:33 am Post subject: Re: Why Sender channel has to be started manually in iSeries |
|
|
Newbie
Joined: 13 Jul 2005
Posts: 6
|
Hi,
Ya, Once the sender channel started it stays running. But why it should be started manually.
Also, While box is going to backup, the following things are done using calling CL program
- Ends all Queue Manager Command Srvrs
- Stops all Queue Manager Channels
- Record all Queue Manager Images
- Ends all Queue Managers
- Ends all Queue Manager Listeners
- Ends QMQM Subsystem
While box is coming from backup, the following things are done using calling CL program
- Starts QMQM Subsystem
- Starts all Queue Managers
- Starts all Queue Manager Listeners
- Starts all Channel Initiators
- Starts all Channels
- Starts all Command Servers
Regards,
Prakash |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Oct 18, 2005 5:01 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Quote: |
trigger type - *ALL,
|
All? You mean EVERY I guess......but it should be FIRST. |
|
| Back to top |
|
|
| sprakashit |
| Posted: Tue Oct 18, 2005 5:11 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2005
Posts: 6
|
Yes, you are right..
Trigger Type is *FIRST not *ALL ( i.e.. EVERY) |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Oct 18, 2005 6:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
(1) I you don not need Process "P" defined, so delete that attribute from the XMITQ.
(2) Did you specify initq 'I' on the STRMQMCHLI command?
_________________
-wayne |
|
| Back to top |
|
|
| sprakashit |
| Posted: Tue Oct 18, 2005 7:56 pm Post subject: |
|
|
Newbie
Joined: 13 Jul 2005
Posts: 6
|
Yes, I specify the 'Init Queue name' and 'Queue Manager name' to start the channel initator using STRMQMCHLI.
But I can't understand why we need to delete the process attribute from XMITQ queue, because it contains
Application identifier: AMQRMCLA [MCA name]
User data: - Sender Channel name - C
Isn't these things not required ? |
|
| Back to top |
|
|
| wschutz |
| Posted: Wed Oct 19, 2005 2:37 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Sorry, my mistake  apparently (at least according to the doc) you do need a process def on iSeries.
Do you have triggering enabled on your xmitq?
CRTMQMQ QNAME(MYXMITQ) QTYPE(*LCL) MQMNAME(MYQMGR) +
PRCNAME(MYPROCESS) TRGENBL(*YES) INITQNAME(MYINITQ) +
USAGE(*TMQ)
_________________
-wayne |
|
| Back to top |
|
|
| Carl Bloy |
| Posted: Wed Oct 19, 2005 6:50 am Post subject: |
|
|
Acolyte
Joined: 16 Dec 2003
Posts: 69
Location: England
|
If my memory serves me right??
I seem to remeber there was an issue with channels not starting after a queue manager restart on iseries in 5.2. I thin kthis was fixed in a later CSD, don't remeber which one as it was a while ago now....
_________________
Regards
Carl |
|
| Back to top |
|
|
| sprakashit |
| Posted: Sat Oct 22, 2005 12:16 am Post subject: |
|
|
Newbie
Joined: 13 Jul 2005
Posts: 6
|
I can able to resolve this issue.
When the channel is in 'STOPPED' state, it won't be started automatically by the channel initiator. The channel should be in 'INACTIVE' state.
Also, process name need not be specified in the XMITQ attribute. |
|
| Back to top |
|
|
|
|
