| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| cluster over Wan or not |
« View previous topic :: View next topic » |
| Author |
Message
|
| George Carey |
 Posted: Tue May 24, 2011 12:58 pm Post subject: cluster over Wan or not |
 |
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
An MQ best practice advisory note some time ago spoke to the wisdon of using sdr/receiver channels over WANs to connect two separately administered entities and not attempt to use cluster channels across WANs ... with the inherent administrative conflicts and dependencies, as well as additional complexities in recovering a misbehaving cluster channel( whether caused by admin error or MQ bug) and further complicated by where the full and partial repositories might or should be placed. (never mind the firewall rules and NATing issues that would need to be resolved)
A friendly partner, however, is pushing to do just that for ease of 'simple', high speed automatic HA connectivity solution between sites. Beside the in-appropriateness of this in general it is also a very low volume traffic connection which makes it even less appropriate. I am wanting to suggest an alternative.
Alternative: Could not under MQ v7 sdr/rcvr channels be defined with alternative destination points being used (e.g. conname ('IP1(p1)', 'IP2(p2)') . This is the case with client svrconn channels, but was not sure about sdr/rcvr channels. I believe QMGR aliases would have to be defined on target servers if this is doable at all.
Anyone tested this and is it doable or not for sdr/rcvr channels. It would be a nice HA option between WAN connected sites in lieu of cluster channels if it is.
Thoughts and comments solicited. (note also MI QMGRs are not an option)
GTC
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue May 24, 2011 1:57 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Channel Sequence numbers will not allow you to implement your idea, for sndr/rcvr or clsndr/clsrcvr channels. The destination QM has to be the "same" QM (i.e a Multi Instance QM).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ramires |
| Posted: Tue May 24, 2011 2:57 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
George, I've this working, a sender channel with two destination ip's pointing to two different queue managers.
If something goes wrong in the network (for example) the sender channel tries a connection to the second ip - where a receiver channel with the same name exists - and goes to running status. In MQ documentation I don't see references to this scenario.
See this:
Ask the Experts Replay: WebSphere MQ Failover on Distributed Platforms. Where the answer to this question "Is using multiple IP addresses in CONNAME to connect to remote queue manager supported when they aren't configured as multi-instance queue managers?" is yes.
Another option is to use MR01 supportpac (I have no experience with it) but has a sample to "...provides a simple channel message exit (referred to as 'the Exit' for the rest of this document), which will cycle through a list of possible CONNAME values"
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue May 24, 2011 3:35 pm Post subject: responses to PeterP and Ramires |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Peter not sure why you are saying clsndr/clsrcvr would not work ? I'm not sure you're clear on what I am asking. I don't wish to use normal clssdr/clsrcvr channel to talk/connect to two remote qmgrs over a WAN (say CQM1, CQM2) for the reasons mentioned. I didn't say it couldn't be done.
What I wish to try to do in lieu of that option is to use MQ v7 connection list option in the (e.g.conname(CQM1,cQM2) )attribute of a channel connection. I know it can be done with a client svrconn channel, I have done it. I was wondering if it could be done with sdr/rcvr channels. And yes I see what you are saying on the sequence numbers I was hoping maybe that a reset channel command would be issued under the covers as part of the channel switch over, again, 'if' the option was there for sdr/rcvr channels.
And Ramires your referenced response:
| Quote: |
| "Is using multiple IP addresses in CONNAME to connect to remote queue manager supported when they aren't configured as multi-instance queue managers?" is yes. |
unfortunately lacks the contexts of mqi(client) or mqs(sdr/rcvr) channel type for the conname attribute.
However, if your statement:
| Quote: |
| "George, I've this working, a sender channel with two destination ip's pointing to two different queue managers. ..." |
is true and your channel is indeed a sdr/rcvr channel can you give me the exact definition you used to make it work ? And how did you handle the channel sequence number issue as pointed out by PeterP or did IBM MQ handle it ?
Rgrds,
GTC
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue May 24, 2011 3:41 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In general, the use of a multiple-valued CONNAME is to only support the use of an MI qmgr at the other end, at least AFAIK.
It might be practically possible to use this to refer to multiple non-MI qmgrs that are distinct, but in general it is a very bad idea.
If the concern is really dealing with talking to multiple destinations over a WAN, where the destination is not actually an officially HA qmgr (either traditional HA or MI)... then you are better off putting in a virtual IP at your end that does the appropriate things (or the inappropriate things, really) to determine if the "main" destination address is "live", and then cause the VIP to "fail over" to the other one when the network layer detects an issue.
If nothing else, causing that many unrelated pings/telnets to someone else's MQ listener will give them incentive to consider a highly available gateway rather than any kind of halfway measures. |
|
| Back to top |
|
|
| ramires |
| Posted: Tue May 24, 2011 4:41 pm Post subject: Re: responses to PeterP and Ramires |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
| Quote: |
| is true and your channel is indeed a sdr/rcvr channel can you give me the exact definition you used to make it work ? And how did you handle the channel sequence number issue as pointed out by PeterP or did IBM MQ handle it ? |
Yes, its a sender/receiver pair. You need a normal sender channel let's say SDRCHL at qmgr QMORIGIN, and the two receiver queue mangers (QMRECEIVER1 and QMRECEIVER2) with a receiver channel with the same name as the sender has: SDRCHL.
In my case the the only issue (until now) was related to the queue manager name in message headers. Message rate is about 2000/3000 msgs/sec. If the connection to QMRECEIVER1 fails the SDRCHL takes a small amount of time to reconnect to QMRECEIVER2. When the connection is established the messages arriving at QMRECEIVER2 were originally tagged (because qremote definitions at QMORIGIN) to QMRECEIVER1, because of this I need a queue manager alias with the name QMRECEIVER1 at QMRECEIVER2 and vice-versa.
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue May 24, 2011 5:27 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Ramires, what about sequence numbers? After QMORIGEN &QMRCVR1 trade 1000 messages the sequence # would be 1000. If the channel switches to QMRCVR2 its receiver channel sequence # would still be 1, no?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ramires |
| Posted: Wed May 25, 2011 12:23 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
Peter, before doing this I was expecting an error with the sequence numbers but it didn't happen. I also found this entry
http://comments.gmane.org/gmane.network.mq.devel/13129
(this is a good forum to follow)
so i tried, and worked.
Supported? Maybe not, the Infocenter doesn't refer this setup, but COONAME description changed sligtly from v6, In v7: "You can provide multiple machine names to configure multiple connections with the same properties. The connections are tried in the order they are specified in the connection list until a connection is successfully established."
I can do a test do check seqnum behavior and post the results.
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| exerk |
| Posted: Wed May 25, 2011 1:09 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
The content of the reply states "...we have done that when connecting to a queue manager that has two separate networks connecting to it for redundancy purposes. We have seen no issues with seq nums...", which implies that it is the same queue manager, not two separate and unique queue managers.
_________________
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 |
|
|
| ramires |
| Posted: Wed May 25, 2011 2:23 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
I just did a new setup to test, creating 3 queue managers, one "sender" qmgr in windows box A, and two "receiver" qmgr using different ports in windows box B.
Did the necessary definitions, sdr chls , xmit q , remote q in the "sender"; rcvr chl, local q, listeners in the "receivers" qmgrs.
I'm using q.exe to put msgs to the remote q. When The channels starts transmitting messages to the "first" remote queue manager, then I stop the receiver channel at that remote queue manager and the sender channel switches to the second queue manager. During this I did several runmqsc dis chs(SDRCHL) here it is (sorry about the size), look for this eye catchers:
at LSTMSGTI(11.04.50) the channel goes into RETRYING
then look for CHSTATI(11.05.02), it enters BINDING and then RUNNING connected to the second "receiver" queue manager!
I believe this behavior is new in 7.0.1.
| Code: |
C:\Documents and Settings\Joao>runmqsc QMSENDER
5724-H72 (C) Copyright IBM Corp. 1994, 2009. TODOS OS DIREITOS RESERVADOS.
Iniciando o MQSC para o gerenciador de filas QMSENDER.
dis chl(SDRCHL) all
1 : dis chl(SDRCHL) all
AMQ8414: Informações sobre Exibir Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
ALTDATE(2011-05-25) ALTTIME(10.31.43)
BATCHHB(0) BATCHINT(0)
BATCHSZ(50) COMPHDR(NONE)
COMPMSG(NONE)
CONNAME(192.168.1.107(2500),192.168.1.107(2501))
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( )
PROPCTL(COMPAT) RCVDATA( )
RCVEXIT( ) SCYDATA( )
SCYEXIT( ) SENDDATA( )
SENDEXIT( ) SEQWRAP(999999999)
SHORTRTY(1000) SHORTTMR(30)
SSLCIPH( ) SSLPEER( )
STATCHL(QMGR) TPNAME( )
TRPTYPE(TCP) USERID( )
XMITQ(XMIT)
dis chs(SDRCHL) all
2 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(13) BATCHSZ(50)
BUFSRCVD(14) BUFSSENT(70)
BYTSRCVD(600) BYTSSENT(53864)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000040E)
CURMSGS(0) CURRENT
CURSEQNO(56) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.14)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(56)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
3 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(14) BATCHSZ(50)
BUFSRCVD(15) BUFSSENT(74)
BYTSRCVD(628) BYTSSENT(56002)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000040F)
CURMSGS(0) CURRENT
CURSEQNO(59) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.18)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(59)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
4 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(16) BATCHSZ(50)
BUFSRCVD(17) BUFSSENT(83)
BYTSRCVD(684) BYTSSENT(62875)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D10000411)
CURMSGS(0) CURRENT
CURSEQNO(66) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.24)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(66)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
5 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(22) BATCHSZ(50)
BUFSRCVD(23) BUFSSENT(104)
BYTSRCVD(852) BYTSSENT(76652)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D10000417)
CURMSGS(0) CURRENT
CURSEQNO(81) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.38)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(81)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
6 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(28) BATCHSZ(50)
BUFSRCVD(29) BUFSSENT(120)
BYTSRCVD(1020) BYTSSENT(86301)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
7 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(29) BATCHSZ(50)
BUFSRCVD(30) BUFSSENT(122)
BYTSRCVD(1048) BYTSSENT(86357)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(NOT RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RETRYING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
8 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(29) BATCHSZ(50)
BUFSRCVD(30) BUFSSENT(122)
BYTSRCVD(1048) BYTSSENT(86357)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(NOT RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RETRYING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
9 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(29) BATCHSZ(50)
BUFSRCVD(30) BUFSSENT(122)
BYTSRCVD(1048) BYTSSENT(86357)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(NOT RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RETRYING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
10 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(29) BATCHSZ(50)
BUFSRCVD(30) BUFSSENT(122)
BYTSRCVD(1048) BYTSSENT(86357)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(NOT RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RETRYING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
11 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(29) BATCHSZ(50)
BUFSRCVD(30) BUFSSENT(122)
BYTSRCVD(1048) BYTSSENT(86357)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(NOT RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RETRYING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
12 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(29) BATCHSZ(50)
BUFSRCVD(30) BUFSSENT(122)
BYTSRCVD(1048) BYTSSENT(86357)
CHSTADA(2011-05-25) CHSTATI(11.03.55)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(000017CC000017D0) LOCLADDR(192.168.1.7(1258))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(NOT RUNNING)
MONCHL(OFF) MSGS(91)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RETRYING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
13 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(0) BUFSSENT(0)
BYTSRCVD(0) BYTSSENT(0)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2500)) CURLUWID(8BCADC4D1000041D)
CURMSGS(0) CURRENT
CURSEQNO(91) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR( )
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.04.50)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(0)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER1) SHORTRTS(999)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(BINDING)
STOPREQ(NO) SUBSTATE( )
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
14 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(0) BATCHSZ(50)
BUFSRCVD(1) BUFSSENT(12)
BYTSRCVD(236) BYTSSENT(10143)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2501)) CURLUWID(8BCADC4D10000501)
CURMSGS(0) CURRENT
CURSEQNO(11) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR(192.168.1.7(1261))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.05.02)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(11)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER2) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
15 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(1) BATCHSZ(50)
BUFSRCVD(2) BUFSSENT(13)
BYTSRCVD(264) BYTSSENT(10171)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2501)) CURLUWID(8BCADC4D10000502)
CURMSGS(0) CURRENT
CURSEQNO(11) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR(192.168.1.7(1261))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.05.02)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(11)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER2) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
16 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(2) BATCHSZ(50)
BUFSRCVD(3) BUFSSENT(16)
BYTSRCVD(292) BYTSSENT(11880)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2501)) CURLUWID(8BCADC4D10000503)
CURMSGS(0) CURRENT
CURSEQNO(13) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR(192.168.1.7(1261))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.05.06)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(13)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER2) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
17 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(4) BATCHSZ(50)
BUFSRCVD(5) BUFSSENT(22)
BYTSRCVD(348) BYTSSENT(16334)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2501)) CURLUWID(8BCADC4D10000505)
CURMSGS(0) CURRENT
CURSEQNO(17) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR(192.168.1.7(1261))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.05.08)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(17)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER2) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
18 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(5) BATCHSZ(50)
BUFSRCVD(6) BUFSSENT(24)
BYTSRCVD(376) BYTSSENT(17205)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2501)) CURLUWID(8BCADC4D10000506)
CURMSGS(0) CURRENT
CURSEQNO(18) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR(192.168.1.7(1261))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.05.10)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(18)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER2) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT)
XQTIME(0,0)
dis chs(SDRCHL) all
19 : dis chs(SDRCHL) all
AMQ8417: Informações sobre exibir Status do Canal.
CHANNEL(SDRCHL) CHLTYPE(SDR)
BATCHES(7) BATCHSZ(50)
BUFSRCVD(8) BUFSSENT(29)
BYTSRCVD(432) BYTSSENT(20049)
CHSTADA(2011-05-25) CHSTATI(11.05.02)
COMPHDR(NONE,NONE) COMPMSG(NONE,NONE)
COMPRATE(0,0) COMPTIME(0,0)
CONNAME(192.168.1.107(2501)) CURLUWID(8BCADC4D10000508)
CURMSGS(0) CURRENT
CURSEQNO(21) EXITTIME(0,0)
HBINT(300) INDOUBT(NO)
JOBNAME(00000340000017A0) LOCLADDR(192.168.1.7(1261))
LONGRTS(999999999) LSTLUWID(0000000000000000)
LSTMSGDA(2011-05-25) LSTMSGTI(11.05.13)
LSTSEQNO(0) MCASTAT(RUNNING)
MONCHL(OFF) MSGS(21)
NETTIME(0,0) NPMSPEED(FAST)
RQMNAME(QMRECEIVER2) SHORTRTS(1000)
SSLCERTI( ) SSLKEYDA( )
SSLKEYTI( ) SSLPEER( )
SSLRKEYS(0) STATUS(RUNNING)
STOPREQ(NO) SUBSTATE(MQGET)
XBATCHSZ(0,0) XMITQ(XMIT) |
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| exerk |
| Posted: Wed May 25, 2011 2:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
When I find the time I'm going to try this myself because it implies that a separate sequence number count per connection is held, the same mechanism as for multiple SDRs into a single RCVR.
_________________
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 |
|
|
| George Carey |
| Posted: Wed May 25, 2011 8:19 am Post subject: conname lists |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
This sounds great Ramires!!
Really appreciate your response effort, here.
I am having a little difficulty finding the eye catchers in your long last post but I can tell from your response you know what you are doing and that it is indeed working (and not two NICs for the same server and thus same QMGR).
I will have to try this between some qmgrs of my own to confirm myself (not sure why I didn't in the first place?)
I am sure this is raising some eyebrows ! Two other points, one a question and one a comment.
1.) Does the conname list capability work on MQ v7(e.g. 7.0.0.2) or just 7.0.1 and greater I forget ?
2.) I was told that MQ v7.0.1 has a pre-req of NFSv4 but in discussion with IBM support that actual support statement was only if you are using MI QMGRs is NFSv4 a support requirement.
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding")
Last edited by George Carey on Wed May 25, 2011 8:27 am; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 25, 2011 8:24 am Post subject: Re: conname lists |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| George Carey wrote: |
| 1.) Does the conname list capability work on MQ v7(e.g. 7.0.0.2) or just 7.0.1 and greater I forget ? |
Only 7.0.1 or greater. Earlier levels of MQ will not like it at all.
| George Carey wrote: |
| 2.) I was told that MQ v7.0.1 has a pre-req of NFSv4 but in discussion with IBM support that actuall support statement was only if you are using MI QMGRs is NFSv4 a support requirement. |
Yes.
Using the CONNAME feature this way is A BAD IDEA. |
|
| Back to top |
|
|
| George Carey |
| Posted: Wed May 25, 2011 8:33 am Post subject: Bad Idea |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Maybe you could give a reason or two Jeff just why it is a BAD IDEA !
Other than it may not be supported. What would they be ?
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
| exerk |
| Posted: Wed May 25, 2011 8:45 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
OK, I've just tried it 'locally' and it works - no need to reset the sequence numbers.
ramires, if you are actually going to use this I suggest using a generic RQMNAME, e.g. RECEIVER, and putting a queue manager alias in each of the recipients - more uniform.
However, like mqjeff this is not something I would advocate the use of as I can see huge scope for confusion.
_________________
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 |
|
|
|
|
|
  |
Goto page 1, 2, 3, 4, 5 Next |
Page 1 of 5 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
