| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [Solved] RCVR channel 2035 error |
« View previous topic :: View next topic » |
| Author |
Message
|
| calvinykw |
 Posted: Fri Oct 07, 2005 9:55 pm Post subject: [Solved] RCVR channel 2035 error |
 |
|
Novice
Joined: 29 Jul 2004
Posts: 12
Location: HK
|
I've encounter a problem when setting a sdr and rcvr channel with using MCAUSER. Message could not be delivered to rcvr side
I've setup two QM in single machine QMA and QMB
in QMA, i created the following things
SDR channel (that point to QMB )
transmission queue TA
remote queue RQ1
qalias Q1a (target queue is remote queue)
in QMB, i created the following things
RCVR channel (with MCAUSER "abc")
qlocal (Q1)
dead letter queue (QMB.DLQ)
i've set the the following rights to user abc
qmgr level:
connect
inq
altuser
Q1 level:
all
When i start all the qm and channel successfully and use the amqsput sample program to put a message to the QAlias 1 by QMA (amqsput Q1a QMA) , the following error is shown in error log of QMB
10/08/05 12:59:02
AMQ9599: Program could not open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object 'QMB.DLQ'
on queue manager 'QMB' by user 'abc' failed with reason code 2035.
ACTION:
Ensure that the queue is available and retry the operation. If the message is
from a remote Queue Manager, check the Message Channel Agent User Identifier
has the correct authority.
----- amqrmmqa.c : 780 --------------------------------------------------------
10/08/05 12:59:02
AMQ9599: Program could not open queue manager object.
EXPLANATION:
The attempt to open either the queue or queue manager object 'Q1' on
queue manager 'QMB' by user 'abc' failed with reason code 2035.
ACTION:
Ensure that the queue is available and retry the operation. If the message is
from a remote Queue Manager, check the Message Channel Agent User Identifier
has the correct authority.
Why the MCAUSER has no authority ? am i missing some rights? And also why the log show the error of DLQ first ?
Last edited by calvinykw on Tue Oct 18, 2005 12:48 am; edited 1 time in total |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Sat Oct 08, 2005 6:01 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Oct 08, 2005 8:55 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You have to add +setall to the QM authorities.
You have to add +put and +setall to the DLQ.
The RCVR MCA needs these capabilities to properly handle incoming messages.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| calvinykw |
| Posted: Wed Oct 12, 2005 1:00 am Post subject: |
|
|
Novice
Joined: 29 Jul 2004
Posts: 12
Location: HK
|
Thanks. It works, but I want to know the effect of adding "setall" for external system to our
QM and queues. e.g. Can external system treat themselves as another user (not the one being set in MCAUSER) when they connect to our QM and get/put messages to our queue? |
|
| Back to top |
|
|
| hopsala |
| Posted: Wed Oct 12, 2005 2:15 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
| calvinykw wrote: |
| I want to know the effect of adding "setall" for external system to our QM and queues. e.g. Can external system treat themselves as another user (not the one being set in MCAUSER) when they connect to our QM and get/put messages to our queue? |
Well, it depends: if you set PUTAUT(DEF), any channel connecting to this RCVR will get MCA authorizations and no other thence; if you set PUTAUT(CTX) then a userid and authorizations will be assigned per message according to MQMD.UserId; I cannot tell which you use, since possibly you put the msg under user "abc", thus the err msg you got doesn't necessarily imply DEF.
Concerning "setall", the System Administration Guide tells us:
| Chapter 10. 127 wrote: |
| If you use the user ID associated with the message, it is likely that this is a user ID from a remote system. This remote system user ID must be recognized by the target system and have the authority to connect to the queue manager, make inquiries, set attributes, and set context options Administration authority (+connect, +inq, +set, and +setall). It must also have authority to put messages and set context information (+put and +setall) for the destination and dead-letter queues. |
| p. 306 wrote: |
| setall Set all context on the specified queue. This is used by special system utilities. |
Keep in mind, that when a chl puts a message to a queue, it has to use MQZAO_SET_ALL_CONTEXT, since it must retain the orignal context info in the message, and not the context of the channel; for example, if the chl just put the message on queue without setting context, the MQMD.PutAppl of all messages would be "runmqchl", regardless of actual message origins.
Hope this clears it up for ya, if you are unfamiliar with the term "context", seek yea the manuals for more details.  |
|
| Back to top |
|
|
| calvinykw |
| Posted: Tue Oct 18, 2005 12:39 am Post subject: [Solved] RCVR channel 2035 error |
|
|
Novice
Joined: 29 Jul 2004
Posts: 12
Location: HK
|
Thanks for your explanation  |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
