| Author |
Message
|
| blovell |
 Posted: Thu Nov 15, 2007 6:26 am Post subject: MQRC 2087 |
 |
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
I have been getting numerous files into my DLQ from a specific Remote QMGR. The message descriptor is complaining of 2087 errors. Outgoing data to the remote QMGR is fine. Problem only appears when the customer passes data into my RCVR Channel. Below is connection scenario
Data arrives into my QMGR on RCVR Channel contact admin.ELSTEST01.T1
Data is suppose to be written to my QLOCAL QM1.FROM.QM2
Outbound data goes to QREMOTE (QM1.TO.QM2)
XMITQ(contact admin)
Data goes out SDR Channel (ELSTEST01.contact admin.T1)
****OUTPUT FROM DLQ******
****Message descriptor****
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 4
Expiry : -1 Feedback : 2087
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 0 Persistence : 1
MsgId : X'414D5120454C5354455354303120202045F5B63D202D5B02'
CorrelId : X'414D5120514D4E415330333120202020473A9CC02000B101'
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'contact admin '
** Identity Context
UserIdentifier : 'intercope '
AccountingToken :
X'494E544552434F50452020202020202020202020202020202020202020202020'
ApplIdentityData : ' '
** Origin Context
PutApplType : '6'
PutApplName : 'amqcrsta_nd '
PutDate : '20071114' PutTime : '14582183'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
_________________
Bradley M. Lovell |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Nov 15, 2007 6:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
This is a name resolution problem.
It means that the message arrived at your queue manager, with a destination for a different queue manager, and your queue manager can't find that different queue manager.
You need to make sure you know where the messages are supposed to go, and then determine what needs to be done to fix the problem. This could be a matter of changing the sending app, or of changing definitions on the remote qmgr or on your local qmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| blovell |
| Posted: Thu Nov 15, 2007 6:41 am Post subject: |
|
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
As the QLOCAL does nothing but accumulate the incoming data from our clients, I can only assume the problem lies with the Remote QMGRS, QREMOTE, or XMITQ. **The only thing that bothers me is when the customer points their SDR to my RCVR on the production QMGR this problem goes away. (The sames queues are defined on the production queue, I have compared them and they are the same) I fear something is different however.
_________________
Bradley M. Lovell |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 15, 2007 6:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So, the sender changes nothing about their application, except which queue manager their channels are connected to... ?
Which means that when the message arrives, it's addressed to a specific qmgr. Depending on which queue manager the channels are pointing to, the receiving queue manager may or may not be the same...
Create a QREMOTE on your receiving side. Name it after your PRODUCTION QMgr. Set the RQMNAME of the QREMOTE to the name of the local qmgr.
Do not set the RQNAME on the QREMOTE.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Nov 15, 2007 7:32 am Post subject: |
|
|
Guest
|
2087 MQRC_UNKNOWN_REMOTE_Q_MGR
This is not a queue name resolution failure. Rather, it is the failure of the RCVR ends MCA receiving an inbound message, asking "am I on the queue manager named in the transmission queue neader (XQH)?" and discovering that it is not. The MCA then drives name resolution to see if there is an object definition for the queue manager name.
The prior post is asking you to create a queue manager alias that resolves the incorrect queue manager name to the correct one.
Examine the Dead Letter Header for these messages. It will contain the name of the queue manager that the message is destined for. If the queue manager name is NOT the name of the queue manager where the message arrives, the message goes to the DLQ if there is no name resolution. |
|
| Back to top |
|
|
| tleichen |
| Posted: Thu Nov 15, 2007 7:50 am Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| bruce2359 wrote: |
2087 MQRC_UNKNOWN_REMOTE_Q_MGR
....Examine the Dead Letter Header for these messages. It will contain the name of the queue manager that the message is destined for. If the queue manager name is NOT the name of the queue manager where the message arrives, the message goes to the DLQ if there is no name resolution. |
And just as a reminder, queue manager names are case-sensitive! 
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Nov 15, 2007 7:54 am Post subject: |
|
|
Guest
|
| Quote: |
| And just as a reminder, queue manager names are case-sensitive! |
This also explains why Vanna White has it so easy on Wheel of Fortune. |
|
| Back to top |
|
|
| blovell |
| Posted: Thu Nov 15, 2007 8:09 am Post subject: |
|
|
Acolyte
Joined: 08 Feb 2006
Posts: 63
Location: Alpharetta, GA
|
Thanks for all the responses. After gather the Queue Params for the clients QREMOTE, and XMITQ we found they were specifying an invalid RQMNAME in their QREMOTE. That will get you every time.
_________________
Bradley M. Lovell |
|
| Back to top |
|
|
|
|
