Author |
Message
|
dusktildawn |
Posted: Thu Nov 20, 2014 8:17 am Post subject: MQ Channel - Not Starting Automatically |
|
|
Novice
Joined: 13 Nov 2014 Posts: 15
|
I currently have MQ channels that do not start automatically when a message hits the Transmission Queue after going into 'IDLE' status for being inactive for 9000 seconds. This is preventing message reposnses from working. What can be done to resolve this?
FYI - MQ sender and receiver channels are set up to work between System i and System p systems. Regarding System i, we have backups that take place bringing down and bringing back up the channels. With System p, no stops and starts take place, but the MQs should start automatically when a message hits the queue during the business day.
Any assistance here will be greatly appreciated. Thanks in advance. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Nov 20, 2014 8:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
are the channels triggered? |
|
Back to top |
|
 |
dusktildawn |
Posted: Thu Nov 20, 2014 8:49 am Post subject: MQ Channel - Not Starting Automatically |
|
|
Novice
Joined: 13 Nov 2014 Posts: 15
|
No, they are not triggered. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Thu Nov 20, 2014 8:53 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
They should be triggered if you want them to start when a message arrives on the XMITQ. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
JosephGramig |
Posted: Thu Nov 20, 2014 9:30 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
On distributed, the first (lexical order) channel that reads the XMITQ will be the one that is started (in case you have mistakenly defined more than one channel to read the XMITQ).
On z/OS, you better put the channel name in the TRIGDATA and it wouldn't hurt to do that on distributed. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Nov 20, 2014 9:42 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
|
Back to top |
|
 |
dusktildawn |
Posted: Thu Nov 20, 2014 10:10 am Post subject: MQ Channel - Not Starting Automatically |
|
|
Novice
Joined: 13 Nov 2014 Posts: 15
|
Okay, I will ask my peer to trigger the channels to see if that works.
As for the TRIGDATA parm, we did change it recently to the correct channel.
Thanks for the link. Maybe I can check the details of the transmission queues to see if the channel is set since no prcess definition exists. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Nov 20, 2014 11:20 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
You don't need a Process def to trigger channels. But you wil need an initiation queue, and a channel initiator monitoring that initq. _________________ 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 |
|
 |
dusktildawn |
Posted: Thu Nov 20, 2014 1:02 pm Post subject: MQ Channel - Not Starting Automatically |
|
|
Novice
Joined: 13 Nov 2014 Posts: 15
|
Hi, I have yet to to find out when the triggering is set, etc.
The INITQ is set to its default as in the link. Not sure what you mean by channel initiator. Do you mean the channel that has the XMITQ assigned? I was also thinking maybe the INPROC (1) and OPPROC(2) were also to deal with this issue, but most likely not. Am I right? |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Nov 20, 2014 1:10 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Nov 20, 2014 1:21 pm Post subject: Re: MQ Channel - Not Starting Automatically |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
dusktildawn wrote: |
Hi, I have yet to to find out when the triggering is set, etc.
The INITQ is set to its default as in the link. Not sure what you mean by channel initiator. Do you mean the channel that has the XMITQ assigned? I was also thinking maybe the INPROC (1) and OPPROC(2) were also to deal with this issue, but most likely not. Am I right? |
The channel initiator is an IBM-supplied trigger monitor application designed to start channels. You can create a channel initiator with MQSC commands (the preferred method), or start runmqchi manually.
Your XMITQ definition identifies the channel name to be started, and the initiation queue where the trigger event message is to be put. The channel initiator you start monitors the initiation queue, and starts the channel. _________________ 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 |
|
 |
dusktildawn |
Posted: Fri Nov 21, 2014 6:59 am Post subject: MQ Channel - Not Starting Automatically |
|
|
Novice
Joined: 13 Nov 2014 Posts: 15
|
Yes, I understand. The channel initiator is set up, so that's good. The XMITQ parms were changed to the correct channels last week, so I got that done.
It appears that the channels are now triggered since yesterday, but the channels did not activate automatically this morning when a message was put in the queue. Do you think the System i recycles may be disrupting the System p triggered channels? |
|
Back to top |
|
 |
JosephGramig |
Posted: Mon Dec 01, 2014 10:41 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
On the System p Qmgr, what are the channel stanzas in the qm.ini file? |
|
Back to top |
|
 |
dusktildawn |
Posted: Mon Dec 01, 2014 12:01 pm Post subject: MQs not starting automatically |
|
|
Novice
Joined: 13 Nov 2014 Posts: 15
|
Hi, this has been resolved. It turned out there was an old MQ that was attampting to connect...
This is now closed. Thanks all! |
|
Back to top |
|
 |
|