| Author |
Message
|
| cicsprog |
 Posted: Wed Mar 30, 2005 1:37 pm Post subject: Mutiple Senders to single Receiver Channel |
 |
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
We do not have Central MQ Administration. I am
the MQ Admin on z/OS. On a single z/OS MQM
named MQAB I have a single Receiver Channel
called:
COGFTTP.MQAB.00
There are multiple Windows MQM’s that have
created Sender Channels using this same name -
COGFTTP.MQAB.00 that go to MQAB.
Here is the display from MQAB:
Channel name Connection name
Start time Messages
COGFTTP.MQAB.00
COGFTTP.MQAB.00 9999999999 (I Changed these IPss for the post)
2005-03-30 07.14.15 266
COGFTTP.MQAB.00 9999999999 (I Changed these IPss for the post)
2005-03-30 06.18.08 672
COGFTTP.MQAB.00 9999999999 (I Changed these IPss for the post)
2005-03-30 11.17.25 8
COGFTTP.MQAB.00 9999999999 (I Changed these IPss for the post)
2005-03-30 10.55.24 20
* Remaninder of display
State
Last message time Type Disposition
CHANNEL PRIVATE MQAB
RUN
2005-03-30 13.32.40 RECEIVER PRIVATE MQAB
RUN
2005-03-30 13.33.56 RECEIVER PRIVATE MQAB
RUN
2005-03-30 13.00.24 RECEIVER PRIVATE MQAB
RUN
2005-03-30 13.20.23 RECEIVER PRIVATE MQAB
I don’t think this is a valid configuration.
It has always been my understanding that you
can only have a single Sender/Receiver pair
between two MQM’s - not multiple Senders
using a single Receiver. Is my understanding
correct?
If my understanding is correct, could messages
be lost with this above configuration?
In addition, the Windows Admin named all his MQM's
the same name COGFTTP...oh the humanity of it all. |
|
| Back to top |
|
 |
| JLRowe |
| Posted: Wed Mar 30, 2005 1:55 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| Nope, you can have multiple senders going to one receiver channel, it is valid. Look at the channel status to see the status of each sender. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Wed Mar 30, 2005 2:47 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
I just happen to notice on my MQM, MQAB, that there is a
Sender of MQAB.COGFTTP.00 with an XMITq of COGFTTP. Not that plays into the mix.
So that makes multiple Windows MQM's with the same QManager name of COGFTTP. With each of those having a Sender Channel of COGFTTP.MQAB.00. And my single MQM, MQAB, with a Receiver of COGFTTP.MQAB.00. |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Mar 30, 2005 3:36 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| So that makes multiple Windows MQM's with the same QManager name of COGFTTP. With each of those having a Sender Channel of COGFTTP.MQAB.00 |
Not necessarily. The channel name can be anything, up to 20 characters, so every QM, with different QM names could define a sender channel called: COGFTTP.MQAB.00. But that could be a nightmare to administer. Also, your sender channel, MQAB.COGFTTP.00, can only connect to a single QM. Look at the CONNAME to see where.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| cicsprog |
| Posted: Wed Mar 30, 2005 3:52 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Did DISPLAY CHSTATUS on each COGFTTP.MQAB.00 Receiver. Different
IPs, yet same MQM QManager name of COGFTTP.
Channel name . . . . . . . : COGFTTP.MQAB.00
Channel type . . . . . . . : RECEIVER
Disposition . . . . . . . . : PRIVATE MQAB
Connection name . . . . . . : 9999999999 (Changed for post)
Remote queue manager . . . : COGFTTP
Transmission queue . . . . :
Status . . . . . . . . . . : RUN
Last sequence number . . . : 0
Last LUW ID . . . . . . . . : 0000000000000000
Indoubt . . . . . . . . . . : NO
Current messages . . . . . : 0
Current sequence number . . : 492
Current LUW ID . . . . . . : BEBB4642100052C9 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 30, 2005 7:34 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| cicsprog wrote: |
Did DISPLAY CHSTATUS on each COGFTTP.MQAB.00 Receiver. Different
IPs, yet same MQM QManager name of COGFTTP.
Channel name . . . . . . . : COGFTTP.MQAB.00
Channel type . . . . . . . : RECEIVER
Disposition . . . . . . . . : PRIVATE MQAB
Connection name . . . . . . : 9999999999 (Changed for post)
Remote queue manager . . . : COGFTTP
Transmission queue . . . . :
Status . . . . . . . . . . : RUN
Last sequence number . . . : 0
Last LUW ID . . . . . . . . : 0000000000000000
Indoubt . . . . . . . . . . : NO
Current messages . . . . . : 0
Current sequence number . . : 492
Current LUW ID . . . . . . : BEBB4642100052C9 |
If your mq admin named the qmgr on each of the incriminating windows boxes the same this is possible but is setting you up for a nightmare.
There is no way of returning a response to the right qmgr if they are all called the same.
There is nothing wrong in having all the win qmgrs using the same channel to send to you. Makes for less admin. However each qmgr should have its own name. Then you could setup a default path to each of those and a request response pattern would work fine again.
Enjoy  |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Mar 30, 2005 8:40 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
| Quote: |
| There is no way of returning a response to the right qmgr if they are all called the same. |
In fact, all replys would go to a single QM, because cicsprog stated that there is a single channel "MQAB.COGFTTP.00" & XMITQ "COGFTTP" set up.
As I originally stated:
| Quote: |
| a nightmare to administer |
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kman |
| Posted: Wed Mar 30, 2005 11:42 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
yeah.. and the sender channel would have a conname attrib, which would be the hostname with and ip port if not default 1414. So yes.. it only goes to one queue manager.
Unless all the windows also carry the same hostname, or same ip... or the dns always would resolve to all windows... which mean.. how did they do that.
Yes... it's a nightmare for you. |
|
| Back to top |
|
|
| cicsprog |
| Posted: Thu Mar 31, 2005 3:49 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Thanks for the replys. The reason I asked the orginal question was because I would have NEVER setup the configuration in that manner. I have always setup unique channels names between MQM's and have no like MQM names on z/OS.
I have stood on the Central Admin soap box before in this company...to no avail. So the application and application production support teams setup non-z/OS MQM's.
Regards |
|
| Back to top |
|
|
|
|
