| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| How to setup this |
« View previous topic :: View next topic » |
| Author |
Message
|
| PeterPotkay |
 Posted: Tue Feb 15, 2005 5:08 pm Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
QM1 sends a message to QM2. That message asks for COA and COD.
When the COA message is generated on QM2, it is put with the same authority as the putter of the original message (this putter being the RCVR MCA on the destination QM).
Unless you are running your RCVR channel with the MCAUSER value set to something other than blank, the RCVR is running with the ID that started it, "mqm" (MUSR_MQADMIN on Windows). "mqm" has full authority to do any put on any system, so it works and the COA message gets sent. QM2 has no problem sending a message put by mqm (or MUSR_MQADMIN)
When the COD message is generated by QM2, it is put with the same authority as the MQMD.UserIdentifier of the original message application message. If that ID does not have authority on QM2, the message goes to the DLQ on QM2 with a 2035.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| kman |
| Posted: Tue Feb 15, 2005 5:17 pm Post subject: |
|
|
Partisan
Joined: 21 Jan 2003
Posts: 309
Location: Kuala Lumpur, Malaysia
|
Peter,
He is having problem with COA. Not COD.
I agree, you'll never going to get 2035 with COA.  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Feb 16, 2005 8:39 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Huh. well if QM1 is send a message to QM2, and the COA is going to the DLQ on QM2, the only thing I can think of is that the RCVR channel on QM2 is running with an MCAUSER of XYZ, and XYZ can put to the destination queue on QM2, but XYZ has no rights to put to the XMITQ back to QM1.
What is the MCAUSER value on the RCVR channel on QM2?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Feb 16, 2005 8:43 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Or, his RCVR channel is running with Put Authority set to Context, which means the RCVR channel is trying to put the COA not as mqm, not as an ID in the MCAUSER of the RCVR, but as the incoming MQMD_Identifier ID, in which case it acts like a COD report, and the QM1 User ID needs to be defined on QM2.
Put Authority set to Context is a big waste of time. If you have it set, change it back to Default. It offers you ZERO protection, and only cause problems like this one.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| srvm |
| Posted: Wed Feb 16, 2005 10:20 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2004
Posts: 43
|
Peter,
Yes, you are correct. I have RCVR channel w/ MCAUSER defined. THis user ONLY has PUT access to destination Q. I will give this user access to PUT on XMITQ.
Thank you for a detailed explanation.
FYI, RCVR channel is running with DEF PUTAUTH, not CTX.
Raj |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
