An XMS application
cannot connect to a queue manager (not authorized)
The XMS C/C++
and XMS .NET clients
may have different behavior from that of theWebSphere MQ JMS
client. Therefore, you may find that your XMS application
cannot connect to your queue manager, although your JMS application can.
- A simple solution to this problem is to try using a userid that is no
more than 12 characters long and is authorized completely in the queue manager's
authority list. If this solution is not ideal, a different but more complex
approach would be to use security exits. If you need further help on this
issue, contact IBM Support for assistance.
- If you set the XMSC_USERID property of the connection factory, it must
match the userid and password of the logged on user. If you do not set this
property, the queue manager will use the userid of the logged on user by default.