I am getting this error while connecting to IBM MQ. I know that this is because of privileges, but is there any way just to check the connection with IBM MQ?

Please suggest.

9 Answers

The 2035 suggests that your connection is getting to the QMgr. If you had the wrong channel name, host or port you would get back a 2059. The 2035 means that the connection made it to the listener, found a channel of the name that was requested and attempted a connection.

If you want to test past this point it will be necessary to either authorize the ID that you are using to connect or to put an authorized ID in the MCAUSER attribute of the channel.

For a detailed explanation of how the WMQ security works on client channels, see the WMQ Base Hardening presentation at .

1

If you enable authorization messages then the 2035 will show up in the event queue. Then you can look at the message and see what ID was used to connect and what options were used too. The 2035 might be because you asked for set authority on the queue manager or something else you aren't supposed to have. The authorization messages wil show you that.

1

You can also resolve this By setting mcauser('mqm') .. i was able to overcome 2035 error.

Define channel (channel1) chltype (svrconn) trptype (tcp) mcauser(‘mqm’)

Esp thanx to my SENIOR Bilal Ahmad (PSE)

1

You have to check the privileges with an MQ administrator.

I have been struggling with this for ages too. Eventually I found this solution. (If you can call turning off authentication a solution.)

I am using version - IBM Websphere 9.1.0.201807091223

From IBM's website they advise turning connection authentication off!!!

Resolving the problem Disable channel authentication

You will need to disable connection authentication, at least temporarily. There are known issues in FTM for Check with regard to using MQ connection authorization. These problems are actively being addressed and fixes will appear in a future fix pack. The target is fixpack 3.0.0.8.

Steps to disable connection authentication: Open MQ command console and type runmqsc ALTER AUTHINFO(SYSTEM.DEFAULT.AUTHINFO.IDPWOS) AUTHTYPE(IDPWOS) CHCKCLNT(NONE) CHCKLOCL(NONE) Restart the queue manager for this change to take effect.

Source

On this topic if you are using MQSeries 9.1 in a test or development environment you can disable channel authentication with the following approach : . Launch MQ command line utility with the following : runmqsc (for example runmqsc QM1) . Disable authentication for all channels with the following command ALTER QMGR CHLAUTH (DISABLED)

For a Q/Q-manager running on Windows, you may have to create the user on the Q/Q-manager machine [i.e. create a user on the Q-machine to match the user on the Q-client machine], and then add that user to the 'mqm' group on that machine.

Steps:

1. Ensure that the domain user that is being used to create the Q CLIENT [i.e. the user that the Q-client app is running under] also exists on the box with the Q/Q-manager. You may be able to just create a local user on the Q/Q-manager box [, or you may have to do some more complicated creation of an Active Directory user - I can't help you there].

2. On the Q/Q-manager box, add the user you have just created [or the existing one, if it already exists] to the mqm group. [On a Windows server box you will need to use the Microsoft Management Console (1. 'mmc' from the command line, 2. File > Add/Remove SnapOn > Local Users & Groups, 3. add user to group)]. The 'mqm' group should already exist on the Q/Q-manager machine.

3

You can use dspmqaut to check the grant. Below is the sample to give user poc access to Queue Manager QM1 and Queue LQ1

 # check the access right of user POC to QM1 dspmqaut -m QM1 -n LQ1 -t q -p poc # if you want to give access, you should use setmqaut -m QM1 -n LQ1 -t q -p poc <access Types> # eg (put everything - in the real live scenario, choose only what you want to grant) : setmqaut -m QM1 -n LQ1 -t q -p poc +put +get +browse +inq +set +crt +dlt +chg +dsp +passid +setid +setall +clr 

Then dont forget to restart QM1 with

 endmqm -i QM1 strmqm QM1

Finally, you should be able to proceed without error 2035.

2

Error MQRC 2035 basically means that your application has been able to connect to the queue manager, however due to certain absence of permissions/authorizations, it was unable to put/get/publish/subscribe messages.

To resolve this, at first, try these steps in order to disable the authorizations from queue manager and channel. Use this only if it isn't a production queue manager.

1. Always check the queue manager logs. It tells you exactly where you need to look into, and resolve the issue.

2. In this case, generally, you can issue the following commands after doing a runmqsc on the queue manager :

   ALTER QMGR CHLAUTH(DISABLED)

Then set the chckclnt object(under authinfo) to optional

3. DISPLAY QMGR CONNAUTH
   DISPLAY AUTHINFO(name-from-above) ALL //name from the first commands
   ALTER AUTHINFO(name-from-above) AUTHTYPE(IDPWOS) ADOPTCTX(YES)
   ALTER AUTHINFO(name-from-above) AUTHTYPE(IDPWOS) CHCKCLNT(OPTIONAL)
   REFRESH SECURITY TYPE(CONNAUTH)

4. SET CHLAUTH('*') TYPE(BLOCKUSER) ACTION(REMOVEALL)

   This helps remove any blocks that the channel is creating against any user.

    SET CHLAUTH(your channel name) TYPE(ADDRESSMAP) ADDRESS('*') USERSRC(CHANNEL)

This should resolve your issue, since we have disabled every authorization that an application has to pass in order to do anything on a queue manager.

Now, in case you are using a production queue manager, NEVER remove authorizations. Go, and right click on any QM that you have configured in your MQ explorer. Go to the QM authority, and authority records. Click on create new user, and give the same name as the username your application is using. Select all the checkboxes, then copy from the space below all the commands that are given. Namely, setmqaut. Edit with your queue manager name, and issue them!

----Never give up, the answer is where you have not looked yet--------

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy