Support Article
Connect MQ fails due to setid command
SA-91368
Summary
User Connect-MQ fails when Pega sends the setid command to MQ while connecting. Pega uses the setid command while sending the message to MQ.
Error Messages
Could not connect to request queue : IDPO.ICS.IN.QA01
MQJE001: Completion Code '2', Reason '2035'. - Incorrect username or password.
MQ error
AMQ8077: Entity 'mquser' has insufficient authority to access object.
EXPLANATION:
The specified entity is not authorized to access the required object. The
following requested permissions are unauthorized: setid
ACTION:
Ensure that the correct level of authority has been set for this entity against
the required object, or ensure that the entity is a member of a privileged
group.
The specified entity is not authorized to access the required object. The
following requested permissions are unauthorized: setid
ACTION:
Ensure that the correct level of authority has been set for this entity against
the required object, or ensure that the entity is a member of a privileged
group.
Steps to Reproduce
1. Create a Connect-MQ rule
2. Send the messages using the Connect-MQ rule
Root Cause
The user who connects to MQ does not have the permission to execute the command according to the user's MQ policy.
Resolution
Perform the following local-change:
Set the below Dynamic System Settings:
- Request queue mq/oo_request : MQC.MQOO_OUTPUT
Value = 16
- Request queue mq/pmo : MQC.MQPMO_NONE
Value = 0
Published October 15, 2019 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.