| Author |
Message
|
| sebastia |
 Posted: Wed Jan 09, 2008 1:49 am Post subject: transmit queue changes to GET(DISABLED) |
 |
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
We have a Transmit Channel
from a MQ v 6.0.1.0 to a Host that has MQ v 5.3
Tha queue and the channel were working until yesterday.
Today I observe that when I stop the channel (CH.TO.MQ1B)
the attribute "GET" of the transmit queue (MQ1B)
changes to "GET(DISABLED)"
*** any clue on why is it hapening ??? ***
=========================================
8 : display ql(MQ1B) all
AMQ8409: Display Queue details.
QUEUE(MQ1B) TYPE(QLOCAL)
ACCTQ(QMGR) ALTDATE(2008-01-09)
ALTTIME(10.42.19) BOQNAME( )
BOTHRESH(0) CLUSNL( )
CLUSTER( ) CLWLPRTY(0)
CLWLRANK(0) CLWLUSEQ(QMGR)
CRDATE(2006-06-16) CRTIME(08.19.10)
CURDEPTH(0) DEFBIND(OPEN)
DEFPRTY(0) DEFPSIST(YES)
DEFSOPT(SHARED) DEFTYPE(PREDEFINED)
DESCR( ) DISTL(NO)
GET(DISABLED) HARDENBO
INITQ(SYSTEM.CHANNEL.INITQ) IPPROCS(0)
MAXDEPTH(500000) MAXMSGL(104857600)
MONQ(QMGR) MSGDLVSQ(PRIORITY)
NOTRIGGER NPMCLASS(NORMAL)
OPPROCS(0) PROCESS( )
PUT(ENABLED) QDEPTHHI(80)
QDEPTHLO(20) QDPHIEV(DISABLED)
QDPLOEV(DISABLED) QDPMAXEV(ENABLED)
QSVCIEV(NONE) QSVCINT(999999999)
RETINTVL(999999999) SCOPE(QMGR)
SHARE STATQ(QMGR)
TRIGDATA(CH.TO.MQ1B) TRIGDPTH(1)
TRIGMPRI(0) TRIGTYPE(EVERY)
USAGE(XMITQ)
=========================================== |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jan 09, 2008 2:24 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What happens when you start the channel again?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jan 09, 2008 2:50 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Receiver end says "Running" ...
Sender end says "Retrying" ...
and sender AMQERR01.LOG says
=================================
-------------------------------------------------------------------------------
01/09/08 11:30:19 - Process(696530.1) User(mqm) Program(runmqchl_nd)
AMQ9558: Remote Channel is not currently available.
EXPLANATION:
The channel program ended because the channel 'MQDES01.MQ1B' is not currently
available on the remote system. This could be because the channel is disabled
or that the remote system does not have sufficient resources to run a further
channel.
ACTION:
Check the remote system to ensure that the channel is available to run, and
retry the operation.
----- amqrfpta.c : 340 --------------------------------------------------------
01/09/08 11:30:19 - Process(696530.1) User(mqm) Program(runmqchl_nd)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'MQDES01.MQ1B' ended abnormally.
ACTION:
Look at previous error messages for channel program 'MQDES01.MQ1B' in the error
files to determine the cause of the failure.
----- amqrccca.c : 777 -------------------------------------------------------- |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 09, 2008 2:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
And presumably the error disappears & the channel starts running if the xmitq is manually changed to GET(ENABLED)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jan 09, 2008 3:26 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
No, changing the GET to ENABLED does not fix it
In fact we have fixed it by restarting the Host MQ !
...
but that is something we can do ... once a year only
...
so I wanted to know the reason the queue attrbibute is changed
and by who ... |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 09, 2008 3:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sebastia wrote: |
In fact we have fixed it by restarting the Host MQ !
|
This is Windows isn't it?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jan 09, 2008 3:42 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
the receiver end of the channel is z/OS with mq 5.3
the sender side of the channel is AIX with MQ v 6.0.1.0
the "mq explorer" is on a XP, of course
( but runmqsc on AIX displays the same GET(DISABLED) attribute ! ) |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 09, 2008 3:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sebastia wrote: |
the sender side of the channel is AIX with MQ v 6.0.1.0
|
Then I'll forgo my normal rant! 
I'd consider applying maintenance and seeing if the problem persists. The obvious culprit is the MCA (which I seem to remember changes the parameter on a STOP) but why it's not changing it back I don't know.
Another possibility is some monitoring software on site that's detected the channel going down and responded by "switching off" the queue but that doesn't sound very likely.
My best guess - it's a bug in v6.0.1, try applying maintenance. Your next move is to raise a PMR & that's the first thing they'll tell you to do!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jan 09, 2008 4:02 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Yes, the MCA is under suspiction ...
Cant apply fixes to Host ... and AIX is going to level 6.1 in 1 month or 2 ...
We shall live with the potential problem until then ...
Thanks, Vitor, for you time and patience. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Jan 09, 2008 4:10 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
What are settings like DISCINT or HBINT or KAINT?
if a channel is set to run "forever", problems tend to accumulate resulting in unrecoverable situations. It's better practise to let channels timeout regularly so problems don't accumulate.
just my 2 cents
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| sebastia |
| Posted: Wed Jan 09, 2008 4:28 am Post subject: |
|
|
Grand Master
Joined: 07 Oct 2004
Posts: 1003
|
Michael - you are right : we have DISCINT = 0
and maybe we shall re-consider this value ...
By the way : have you seen the film "number 14", where Johan is the star ?
S. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Jan 09, 2008 4:36 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| sebastia wrote: |
By the way : have you seen the film "number 14", where Johan is the star ?
|
yes! and many more unforgettable moments of "el salvador" 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 09, 2008 4:39 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I have seen this kind of scenario...
Usually it means that one of the channels did not for whatever reason (TCP/IP) disconnect cleanly.
My remedy has always been to stop the sender channel and check the status of all the channel ends. Make sure they are all stopped and there isn't one that says running (stop with mode force in that case is usually sufficient).
Then start the receiving channel first and start the sender...
So far that has always worked. I used to see this much more often when we were having a conversation from 5.3 to MF 2.1. Occasionally (very seldom) from 5.3 to 5.3.1. Haven't seen it yet from 5.3/6.0 to MF 6.0
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 09, 2008 8:59 am Post subject: Re: transmit queue changes to GET(DISABLED) |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| sebastia wrote: |
Today I observe that when I stop the channel (CH.TO.MQ1B)
the attribute "GET" of the transmit queue (MQ1B)
changes to "GET(DISABLED)"
*** any clue on why is it hapening ??? ***
|
When a SNDR channel is anything other than RUNNING or INACTIVE, its XMITQ is Get Inhibited by the SNDR MCA.
MQ working as designed. Figure out what the problem is that is preventing the SNDR chanel from making a connection. The XMITQ being disabled is not the problem.
If the RCVR is running and the SNDR is retrying, it sounds like you aren't using Heartbeats and you aren't using AdoptNewMCA on this channel pair. You should be. And yes, DISCINT=0 is wrong 99.9% of the time.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
