| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| runmqsc -c against a multi-instance qm |
« View previous topic :: View next topic » |
| Author |
Message
|
| Esa |
 Posted: Wed Dec 21, 2016 12:20 am Post subject: runmqsc -c against a multi-instance qm |
 |
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
Hi,
I'm testing client connections to a multi-instance queue manager with runmqsc -c. My CCDT has an entry with a list of connection names in CONNAME. But the client connects only to the first connection name in the list. If I switch over the queue manager, I get AMQ9508 Program cannot connect to the queue manager with no reason code.
If I switch the order of connection names in the CONNAME list, the client connects to the other instance, which is now the first in the list.
Both server and client are running on Red Hat Linux. MQ Server version is 8.0.0.4. MQ Client version is 8.0.0.2.
Is it so that runmqsc does not suppot CONNAME lists in client mode? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Dec 21, 2016 5:19 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
It should. If you can positively point it back to the client list in the ccdt channel, then go ahead and open a PMR. What I suspect though is a poorly defined ccdt.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| umatharani |
| Posted: Thu Dec 22, 2016 4:49 pm Post subject: |
|
|
Apprentice
Joined: 23 Oct 2008
Posts: 39
|
I suspect the problem could be because of the APAR IT09524 if you have created the table using runmqsc -n(i.e. on the client side). Try with a table created from the server or try with a table created on MQ 8003 or higher MQ levels on the client side.
Thanks,
mahesh |
|
| Back to top |
|
|
| Esa |
| Posted: Fri Dec 23, 2016 10:23 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| I tested with CCDT's created with runmqsc -n and on a server running v. 8.0.0.4. I guess I should upgrade the client to version 8.0.0.4 and test if the problem persists. Thanks for the info, this APAR is not mentioned in V. 8 fix list. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
