| Author |
Message
|
| vsathyan |
 Posted: Sun Jun 01, 2014 10:26 pm Post subject: Connect to a queue manager with different name |
 |
|
Centurion
Joined: 10 Mar 2014
Posts: 121
|
Dear all,
Is there a way to connect to a queue manager other than the name it is defined?
For example - If i create a qmgr with name - QMX, is there any configuration setting in the queue manager where i can use a different name in the application configuration file which resolves to the actual queue manager name at the time of connecting?
Example
QMGR Name(Port Number) : QMX(12345) on Server1
App Config
Host Name - Server1
QMGR Name - QMA
Port Number -12345
Channel - QMA.SVRCONN
App Config
Host Name - Server1
QMGR Name - QMB
Port Number - 12345
Channel - QMB.SVRCONN
PS : I know we can connect without providing the queue manager name (just by providing the server name, port number and channel using TAB files), but I want to check if there is any way of connecting to a queue manager using a different name than the actual name defined.
Thank you. |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Jun 02, 2014 12:06 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Try THIS.
_________________
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 |
|
|
| zpat |
| Posted: Mon Jun 02, 2014 12:08 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Queue manager aliases exist, but I don't think they can be used for MQCONN.
The pre-connection exit could presumably change the QM name.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| hughson |
| Posted: Mon Jun 02, 2014 4:46 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| zpat wrote: |
| The pre-connection exit could presumably change the QM name. |
Yup - that's a very good use case for a pre-conn exit.
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| zpat |
| Posted: Mon Jun 02, 2014 4:54 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Are there any complete examples of this exit supplied with MQ?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| hughson |
| Posted: Mon Jun 02, 2014 5:22 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| zpat wrote: |
| Are there any complete examples of this exit supplied with MQ? |
The MQ Product ships amqlcel0.c which is the LDAP lookup sample. This is way bigger an exit than required to just over-ride the queue manager name, but it would at least give you the calling convention for the exit.
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
