| Author |
Message
|
| Manikandan |
 Posted: Tue Nov 23, 2004 3:45 am Post subject: Q Manager alias |
 |
|
Voyager
Joined: 07 Jul 2004
Posts: 78
|
How to create a Queue Manager Alias.
What is the use of creating QM alias.
Pls revert on the same. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Nov 23, 2004 5:15 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Do a search on this subject in the Intercommunications Manual. And please post any specific questions you have after that.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Manikandan |
| Posted: Tue Nov 23, 2004 5:23 am Post subject: |
|
|
Voyager
Joined: 07 Jul 2004
Posts: 78
|
Peter,
I am just looking at a scenario where I have only one Q manager on my side and the remote Mainframe server has a bunch of Queue Managers.
I have to implement the setup as it just uses my single QUeue Manager.
It is a restriction that I will have to use only one Q-manager on myside.
Will the Qmgr alias help here.Looks like it will help.
Please brief me what I will have to do to ensure that With my single Queue Managers I can connect to different Q,Managers on the Mainframe.
Thanks |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Tue Nov 23, 2004 5:29 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
All you need are XMIT queues on your QM named exactly after the names of the remote queue managers. This will allow Name Resolution to take place.
If the XMIT queues need to be named something else, then define QM Aliases that are the same name as the remote queue managers, and have the QM Aliases referance the appropriate XMIT queue. This will allow Name Resolution to take place as well.
In addition, any remote queue definitions on your side can specify an XMITQ directly, in which case it doesn't matter what the XMITQ is called, and in this case you don't need the QM Alias, although it wouldn't hurt you if they were there for other reasons.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Manikandan |
| Posted: Wed Nov 24, 2004 5:29 am Post subject: |
|
|
Voyager
Joined: 07 Jul 2004
Posts: 78
|
Thanks for the suggestions,
I did think to have different transmission queues and different channels for the different queue managers on the other side.
Looks like there is no option for that.
The setup is already defined on the other side.
But still I could not pick up this Qmanager alias concept from the pdf's
It would be great if someone and look the below summary and specify what I will have to do here
The summary looks like
Solaris side
##################
Single Queue Manager-- QMACB
Local Queue -- Q1
REmote Q - Q2
Xmitq - QMBEC
s.channel -- QMACB.QMBEC
r.channel - QMBEC.QMACB
####################
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Mainframe side
###################
Multiple Queue Managers
Queue Manager 1 - QMBEC
Local Q - Q2
Remote Q- Q1
Xmitq - QMACB
s.channel - QMBEC.QMACB
r.channel - QMACB.QMBEC
XXXXXXXXXXXXXXXXXXXXXXXX
Queue manager 2 - QMCEC
Local Q - Q1
Remote Q - Q2
Xmitq - QMCCB
s.channel - QMCEC.QMCCB
r.channel - QMCCB.QMCEC
######################
Queue manager 3 - QMDEC
Local Q - Q1
Remote Q - Q2
Xmitq - QMDCB
s.channel - QMDEC.QMDCB
r.channel - QMDCB.QMDEC
Now everything is defined already on the mainframe side.
Requirements are
1.Single Q-manager on the solaris side
2.No modification on the mainframe side and should modify to configure things to fit to reach all the Queue Managers.
Please help on the same. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Nov 24, 2004 4:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
O.K.
So we'll have to modify the Solaris side.
Assumption 1 -- only 1 QMGR on Solaris we are not adding qmgrs.
Note: when sending messages to MF you will need to impersonate the Reply to QMGR to be not QMACB but QMCCB or QMDCB depending on which qmgr you are sending to.
You need to define on Solaris the corresponding sender /receiver channels
QMCCB.QMCEC QMCEC.QMCCB QMDCB.QMDEC QMDEC.QMCCB
Now you need to set up the alias so that you are recognized as consuming messages for QMCCB and or QMDEC.
def qr(QMCCB) rqmname(QMBCB)
and so on....
Assumption 2: Just create the corresponding qmgrs QMCCB and QMDCB on solaris and setup the communications. You may have to setup default ways to communicate between QMBCB QMCCB and QMBCB and QMDCB depending on the MF channel setup.
Enjoy  |
|
| Back to top |
|
|
| Manikandan |
| Posted: Wed Nov 24, 2004 7:20 pm Post subject: |
|
|
Voyager
Joined: 07 Jul 2004
Posts: 78
|
HOw should I define this alias.
"def qr(QMCCB) rqmname(QMBCB",
please brief |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Nov 25, 2004 1:48 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
| def qr(QMCCB) rqmname(QMBCB) |
This is the alias definition.
It tells the queue manager (QMBCB) where you define the remote queue:
define queue remote(QMCCB) remote queue manager name QMBCB.
So any messages destined to QMCCB arriving at QMBCB will get rerouted to QMBCB. There is no need for a transmission queue as you are rerouting the messages to yourself.... Now you will need to consume the messages ... If they are for a queue that does not exist they will go to the DLQ (and you better have one defined for the qmgr "dis qmgr all").
Read up on the intercommunications manual.
Enjoy |
|
| Back to top |
|
|
|
|
