| Author |
Message
|
| solomon_13000 |
 Posted: Sun Jul 06, 2008 3:39 am Post subject: Multiple Queue Manager Alias |
 |
|
Master
Joined: 13 Jun 2008
Posts: 284
|
I attempted to use a single queue manager alias (middleware) to send messages from HKSAA1S1 to LNJUP1S1 and it works. However from HKSAA1S1 to middleware to middleware to LNJUP1S1 does not seem to work. Is my concept correct?.
Sender QM (HKSAA1S1):
DEFINE QREMOTE(MQW.SAAHK.MTS.RQST) +
DESCR('') +
RNAME(MQW.SAAHK.MTS.RQSTIN) +
RQMNAME(LNJUP1S1) +
XMITQ(HKIP01S1.XMIT.DF) +
DEFPSIST(YES) +
NOREPLACE
DEFINE QLOCAL(HKIP01S1.XMIT.DF) +
DESCR('') +
TRIGDATA(HKSAA1S1.HKIP01S1.DF) +
USAGE(XMITQ) +
TRIGGER +
INITQ('SYSTEM.CHANNEL.INITQ') +
NOREPLACE
DEFINE CHANNEL(HKSAA1S1.UKIP01S1.DF) +
CHLTYPE(SDR) +
DESCR('') +
CONNAME('localhost(2002)') +
XMITQ(HKIP01S1.XMIT.DF) +
NOREPLACE
Middleware QM (UKIP01S1):
DEFINE QREMOTE(LNJUP1S1) +
DESCR('') +
RQMNAME(LNJUP1S1) +
RNAME('') +
XMITQ(HKIP01S1.XMIT.DF) +
DEFPSIST(YES) +
NOREPLACE
DEFINE QLOCAL(HKIP01S1.XMIT.DF) +
DESCR('') +
TRIGDATA(UKIP01S1.HKIP01S1.DF) +
USAGE(XMITQ) +
TRIGGER +
INITQ('SYSTEM.CHANNEL.INITQ') +
NOREPLACE
DEFINE CHANNEL(HKSAA1S1.UKIP01S1.DF) +
CHLTYPE(RCVR) +
DESCR('') +
NOREPLACE
DEFINE CHANNEL(UKIP01S1.HKIP01S1.DF) +
CHLTYPE(SDR) +
DESCR('') +
CONNAME('localhost(2005)') +
XMITQ(HKIP01S1.XMIT.DF) +
NOREPLACE
Middleware QM (HKIP01S1):
DEFINE QREMOTE(LNJUP1S1) +
DESCR('') +
RQMNAME(LNJUP1S1) +
RNAME('') +
XMITQ(LNJUP1S1.XMIT.DF) +
DEFPSIST(YES) +
NOREPLACE
DEFINE QLOCAL(LNJUP1S1.XMIT.DF) +
DESCR('') +
TRIGDATA(HKIP01S1.LNJUP1S1.DF) +
USAGE(XMITQ) +
TRIGGER +
INITQ('SYSTEM.CHANNEL.INITQ') +
NOREPLACE
DEFINE CHANNEL(UKIP01S1.HKIP01S1.DF) +
CHLTYPE(RCVR) +
DESCR('') +
NOREPLACE
DEFINE CHANNEL(HKIP01S1.LNJUP1S1.DF) +
CHLTYPE(SDR) +
DESCR('') +
CONNAME('localhost(2011)') +
XMITQ(LNJUP1S1.XMIT.DF) +
NOREPLACE
Receiver QM (LNJUP1S1):
DEFINE CHANNEL(HKIP01S1.LNJUP1S1.DF) +
CHLTYPE(RCVR) +
DESCR('') +
NOREPLACE
DEFINE QLOCAL(MQW.SAAHK.MTS.RQSTIN) +
DESCR('') +
USAGE(NORMAL) +
DEFPSIST(YES) +
NOREPLACE
Last edited by solomon_13000 on Sun Jul 06, 2008 1:13 pm; edited 1 time in total |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Sun Jul 06, 2008 6:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| does not seem to work. |
Exactly how do you know it doesn't work? What reason codes, error messages have you received? What symptoms? Did you try putting a message to a queue? What happened to the message? Did it go to a dead letter queue?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 6:39 am Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| I attempted to retrieve the message from MQW.SAAHK.MTS.RQSTIN and there was no message in it. So I was wondering is my concept of defining a remote queue definition correct. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jul 06, 2008 7:12 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Are you attempting to multi-hop the message from the qmgr where the message originated (amqsput), transit through another qmgr, and ultimately arrive on a destination queue on a destination qmgr?
By middleware do you mean the qmgrs between the originating and destination qmgr?
You need to do some basic problem-determination:
1) did the message arrive on the originating qmgrs transmission queue?
2) did it leave the xmit queue?
3) did it get sent on the sender channel from the originating qmgrs xmit queue?
4) did it arrive on the next qmgrs receiver channel?
5) did the message end up on the next qmgrs dead letter queue?
6) did you define dead letter queue(s) on all qmgrs?
7) repeat these steps for each in-transit qmgr
For each qmgr:
Look at the error logs on each qmgr. What reason codes, error messages have you received?
What symptoms?
What happened to the message?
Did it go to a dead letter queue?
MQ doesn't lose messages. Messages are either in a transmission queue waiting to be sent down the channel, OR in the destination queue, OR in a dead-letter queue in one of the qmgrs. Look. Do some research.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 8:12 am Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
I am receiving the error:
1 : DISPLAY CHS(HKSAA1S1.UKIP01S1.DF)
AMQ8420: Channel Status not found.
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jul 06, 2008 8:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I am receiving the error |
Please provide more details when you post.
Where are you receiving this? The originating qmgr?
It is not an error. It tells you that the channel you named is not active when you issued the display command. The channel may not have been started, or it may have disconnected.
In prior posts I offered you some basic and specific problem-determination steps, but you appear to ignore them, OR you are not telling me the results. Which is it?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 1:12 pm Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
HKSAA1S1 queue manager. I did the telnet to test the issue of firewall and it appears as blank screen with no error message. I also did the DISPLAY QLOCAL on the (HKSAA1SA) queue manager transmission queue (HKIP01S1.XMIT.DF) to determent the current depth and also I did DISPLAY CHS on the (HKSAA1SA) queue manager sender channel (HKSAA1S1.UKIP01S1.DF) to determent the current status. Also I specified the channel listener as:
runmqlsr -t tcp -p 2002 -m UKIP01S1
runmqlsr -t tcp -p 2005 -m HKIP01S1
runmqlsr -t tcp -p 2011 -m LNJUP1S1
however on the (HKSAA1SA) queue manager transmission queue (HKIP01S1.XMIT.DF) , the current depth keeps increasing. It seems that the channel status for (HKSAA1SA) queue manager sender channel (HKSAA1S1.UKIP01S1.DF) is showing the following status:
1 : DISPLAY CHS(HKSAA1S1.UKIP01S1.DF)
AMQ8420: Channel Status not found.
One MQSC command read.
No commands have a syntax error.
One valid MQSC command could not be processed.
however the status should be running since I already mentioned the trigger option at the (HKSAA1SA) queue manager transmission queue (HKIP01S1.XMIT.DF). Therefore it should trigger the channel.
Last edited by solomon_13000 on Sun Jul 06, 2008 1:50 pm; edited 5 times in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jul 06, 2008 1:18 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What were the results of what you did????
| Quote: |
| HKSAA1S1 queue manager. |
| Quote: |
| I did the telnet to test the issue of firewall. |
What was the result?
| Quote: |
| I also did the DISPLAY QLOCAL to determent the current depth |
Of which queues? What were the results?
| Quote: |
| and also I did DISPLAY CHS to determent the current status. |
Which channels? On which qmgrs? What were the results?
Please be specific.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 1:32 pm Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| I have updated the details above. Also in addition, the middleware is the Queue Manager Definition (QMD). In other words a multi-hop between the sender queue manager (HKSAA1S1) and the receiver queue manager (LNJUP1S1). So the message will travel in this sequence, (HKSAA1S1) sender queue manager to (UKIP01S1) middleware queue manager to (HKIP01S1) middleware queue manager to (LNJUP1S1) receiver queue manager. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 6:44 pm Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
The root cause of the problem is the channel status inactive. I have to start the channel from MQ Explorer. But usually I never face this problem. I only had to run the listener on the command prompt. The rest is taken care by the QM. To start the channel I issued MQSC START CHANNEL(<channel name>).
Last edited by solomon_13000 on Sun Jul 06, 2008 7:36 pm; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jul 06, 2008 7:30 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
To have the channel start when a message arrives in the xmit queue, you need to start a channel initiator (runmqchi). runmqchi is the trigger monitor for starting channels - like runmqtrm is the trigger monitor for starting applications. Refer to the WMQ System Admin manual for details on runmqchi.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 7:40 pm Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| I did issue runmqchi but it displayed an error saying that cannot access the queue manager object. But the MQSC START CHANNEL(<Channel name>) worked well. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sun Jul 06, 2008 7:49 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I did issue runmqchi but it displayed an error saying that cannot access the queue manager object. |
runmqchi -q InitiationQueue -m QMgrName
-q is the initiation queue you named in the xmit queue definition
-m is the queue manager name.
I'd guess that the initiation queue doesn't exist.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| solomon_13000 |
| Posted: Sun Jul 06, 2008 9:45 pm Post subject: |
|
|
Master
Joined: 13 Jun 2008
Posts: 284
|
runmqchi -q SYSTEM.CHANNEL.INITQ -m HKSAA1S1
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
7/7/2008 13:43:19 AMQ9509: Program cannot open queue manager object. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 07, 2008 5:49 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Does the SYSTEM.CHANNEL.INITQ exist?
Is it being used by any other channel initiator instance? Or some other application? Display the attributes of the queue and post here.
What happens is you try to to browse the queue using the supplied utility amqsbcg SYSTEM.CHANNEL.INITQ?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
