Hello,
I need some help to understand the following problem.
environment:
- MQSeries server v5.2 on Win2000 on computerA
- MQSeries client v5.2 on Win2000 on computerB
(btw, same problem happen with v5.1 and v5.2.1)
On client side I send a message with COA/COD. I use SET_IDENTITY_CONTEXT and
The issue is that the COA is sent by the queue manager with the authority of
the queue manager. The COD is sent by the queue manager with the authority
of the user identity in the MD. If this is blank, typically the OAM will
not allow the COD to be sent.
Dave
Instructions for managing your
Thanks David.
Any ideas if this behavior is by design or will it change in future
versions ?
Any reason why aren't both COA and COD sent with the same authority ?
I'd understand if both succeed or both fail. It's strange that COA succeed
and COD fail. (i.e., it's strange that each one is sent
I believe it to be by design (I think my memory of how it works is correct).
I couldn't find a statement in the documentation about this which surprised
me as the MQ docs are generally pretty good about documenting everything you
need to know (though it's not always that easy to find the bit you
Doron,
My guess it is by necessity The COA is produced by the Channel agent (when
working between queue managers), while the COD is produced by the MQGET
command itself. One has the authority of the entity doing the final MQPUT
command, while the other comes from the MQGET. What is commonly done
