| Author |
Message
|
| PaulC |
 Posted: Fri Feb 13, 2009 4:49 am Post subject: chstatus - rqmname() |
 |
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
Hi all,
First post/ first dive in the world of MQ. I've had a quick look around the FAQ's and couldn't find anything about this.
I have set up replication between 2 servers, it all works fine going one way ( the sendq ) but the adminq going the other way totally fails...
A chstatus on the failing sdr channel has a RQMNAME().
I can see messages in the XMITQ but they get no further and the RQMNAME() looks a bit suspect...
Shouldn't there be a remote QM name ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Feb 13, 2009 4:56 am Post subject: Re: chstatus - rqmname() |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PaulC wrote: |
| I have set up replication between 2 servers |
WMQ has no concept of replication, just messages going from one queue manager to another...
| PaulC wrote: |
| , it all works fine going one way ( the sendq ) but the adminq going the other way totally fails... |
...but this sounds a lot like a PM4Data set up, so I'm assuming you're "replicating" files.
A chstatus on the failing sdr channel has a RQMNAME().
| PaulC wrote: |
I can see messages in the XMITQ but they get no further and the RQMNAME() looks a bit suspect...
Shouldn't there be a remote QM name ? |
Maybe not.
You should a) double check the definitions, particually if the sender channels are set to service that xmitq queue, b) compare the definitons in one direction (which work) with the other direction (which don't).
If all else fails, posts the definitions (not the status).
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Feb 13, 2009 4:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
not quite sure what you mean by "replication between 2 servers" - possibly you're referring to the DB2 stuff.
In general, when troubleshooting communications between two queue managers, you should revisit the definitions of all of the objects involved. Confirm that all of the right parameters are set on the sender channel, that all of the right parameters are set on the receiver channel, that any QREMOTE and QALIAS objects are configured correctly, that the QLOCAL being used as an XMITQ has the right USAGE, etc. etc. etc...
in other words, go back over your configuration with a fine toothed comb and doublecheck that each object you defined has the correct values for it's role in the situation.
As you say, it is usually helpful for messages going to a remote qmgr to have an RQMNAME value. |
|
| Back to top |
|
|
| PaulC |
| Posted: Fri Feb 13, 2009 5:02 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
Apologies, when I mean replication I mean it as part of a db2 Q-Rep setup....
I'll go back through the definitions again, I've been going over them all day but I'm probably missing something obvious..
If I can't see it in the next hour or so I'll post them here... |
|
| Back to top |
|
|
| PaulC |
| Posted: Mon Feb 16, 2009 5:25 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
Still getting nowhere, I've included the definitions ( I've altered the queue names, ip etc) but that's all.. There noticable thing is that the XMITQ changes to NOTRIGGER after having a defined triiger on it....
AMQ8409: Display Queue details.
QUEUE(LOCAL_SERVER.ADMINQ)
TYPE(QREMOTE)
ALTDATE(2009-02-13)
ALTTIME(11.14.20)
CLUSNL( )
CLUSTER( )
CLWLPRTY(0)
CLWLRANK(0)
DEFBIND(OPEN)
DEFPRTY(0)
DEFPSIST(NO)
DESCR( )
PUT(ENABLED)
RQMNAME(REMOTE_SERVERQM)
RNAME(REMOTE_SERVER.ADMINQ)
SCOPE(QMGR)
XMITQ(LOCAL_SERVER.XMITQ)
AMQ8409: Display Queue details.
QUEUE(LOCAL_SERVER.XMITQ)
TYPE(QLOCAL)
ACCTQ(QMGR)
ALTDATE(2009-02-16)
ALTTIME(13.12.51)
BOQNAME( )
BOTHRESH(0)
CLUSNL( )
CLUSTER( )
CLWLPRTY(0)
CLWLRANK(0)
CLWLUSEQ(QMGR)
CRDATE(2009-02-12)
CRTIME(14.48.3
CURDEPTH(17)
DEFBIND(OPEN)
DEFPRTY(0)
DEFPSIST(NO)
DEFSOPT(SHARED)
DEFTYPE(PREDEFINED)
DESCR( )
DISTL(NO)
GET(DISABLED)
HARDENBO
INITQ(SYSTEM.CHANNEL.INITQ)
IPPROCS(0)
MAXDEPTH(5000)
MAXMSGL(4194304)
MONQ(QMGR)
MSGDLVSQ(PRIORITY)
NPMCLASS(NORMAL)
OPPROCS(1)
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( )
TRIGDPTH(1)
TRIGMPRI(0)
TRIGTYPE(EVERY)
USAGE(XMITQ)
AMQ8414: Display Channel details.
CHANNEL(LOCAL_TO_REMOTE.CHANNEL)
CHLTYPE(SDR)
ALTDATE(2009-02-12)
ALTTIME(14.47.20)
BATCHHB(0)
BATCHINT(0)
BATCHSZ(50)
COMPHDR(NONE)
COMPMSG(NONE)
CONNAME(xx.xxx.xx.xxx(1414))
CONVERT(NO)
DESCR( )
DISCINT(6000)
HBINT(300)
KAINT(AUTO)
LOCLADDR( )
LONGRTY(999999999)
LONGTMR(1200)
MAXMSGL(4194304)
MCANAME( )
MCATYPE(PROCESS)
MCAUSER( )
MODENAME( )
MONCHL(QMGR)
MSGDATA( )
MSGEXIT( )
NPMSPEED(FAST)
PASSWORD( )
RCVDATA( )
RCVEXIT( )
SCYDATA( )
SCYEXIT( )
SENDDATA( )
SENDEXIT( )
SEQWRAP(999999999)
SHORTRTY(10)
SHORTTMR(60)
SSLCIPH( )
SSLPEER( )
STATCHL(QMGR)
TPNAME( )
TRPTYPE(TCP)
USERID( )
XMITQ(LOCAL_SERVER.XMITQ) |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 16, 2009 5:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PaulC wrote: |
There noticable thing is that the XMITQ changes to NOTRIGGER after having a defined triiger on it....
|
Working as designed; it's in response to a channel failure.
What do the queue manager logs say about the channel?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| PaulC |
| Posted: Mon Feb 16, 2009 9:06 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
| I've just deleted and redefined the queues, placed some data on the remote queue and the expected failure happens but no error logs are generated. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 16, 2009 9:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The xmitq is missing/not showing TRIGGER/NOTRIGGER.
what does dis chstatus show for the channel? What happens when you START CHANNEL? |
|
| Back to top |
|
|
| PaulC |
| Posted: Mon Feb 16, 2009 9:32 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
It was showing NOTRIGGER.. I think it got lost whilst I was formatting the post. 
If I START CHANNEL ( which attempts a connection as I can see TCP activity on the target server ) it just starts the channel and stops. None of the messages move off of the XMITQ.
It seems to me that the problem could be with the TRIGGER, I can see the messages that I put onto the remote queue ( amqsput ) appear on the XMITQ but it just stops there.
The CHSTATUS is ( and I've changed the names to protect the innocent !)
1 : DISPLAY CHSTATUS(LOCAL_TO_REMOTE)
AMQ8417: Display Channel Status details.
CHANNEL(LOCAL_TO_REMOTE) CHLTYPE(SDR)
CONNAME(xxx.xx.xxx.xx(1414)) CURRENT
RQMNAME( ) STATUS(RETRYING)
SUBSTATE( ) XMITQ(LOCAL_TO_REMOTE.XMITQ)
The only thing I noticed was that the RQMNAME was empty. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 16, 2009 9:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The status is RETRYING. It's likely in Long Retry, so nothing will happen until it wakes up.
Look for errors on the RCVR qmgr.
STOP the channel, manually START it again and see what happens. |
|
| Back to top |
|
|
| PaulC |
| Posted: Tue Feb 17, 2009 1:55 am Post subject: |
|
|
Novice
Joined: 13 Feb 2009
Posts: 10
|
Sorted it. SDR and RCV channel were named differently.
Feel free to flame me, slap me and inscribe the word NOOOB across my forehead.
I'll shall hang my head in shame...
Thanks for your help, I'll certainly be hanging around here, I have a lot to learn. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Feb 17, 2009 2:04 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Something I'm sure we've all done before, but if it will make you feel better - 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
