Do you use IBM’s MQRC program? Do you wish it could display more information? I created an application called MQRC2 to fill this need.
MQRC2 application can interpret an MQ reason code number (i.e. 2035), MQ reason code symbol (i.e. MQRC_OBJECT_IN_USE) or AMQ message number (i.e. AMQ4005) and display the relevant information from the WebSphere MQ Messages manual.
Note: The information outputted belongs to IBM. Capitalware takes no responsibility for the content.
C:\Capitalware\MQRC2>mqrc2 2035 2035 (X'07F3') MQRC_NOT_AUTHORIZED Explanation: The user is not authorized to perform the operation attempted: - On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue manager. * On z/OS, for CICS applications, MQRC_CONNECTION_NOT_AUTHORIZED is issued instead. - On an MQOPEN or MQPUT1 call, the user is not authorized to open the object for the option(s) specified. * On z/OS, if the object being opened is a model queue, this reason also arises if the user is not authorized to create a dynamic queue with the required name. - On an MQCLOSE call, the user is not authorized to delete the object, which is a permanent dynamic queue, and the Hobj parameter specified on the MQCLOSE call is not the handle returned by the MQOPEN call that created the queue. - On a command, the user is not authorized to issue the command, or to access the object it specifies. This reason code can also occur in the Feedback field in the message descriptor of a report message; in this case it indicates that the error was encountered by a message channel agent when it attempted to put the message on a remote queue. Completion Code: MQCC_FAILED Programmer Response: Ensure that the correct queue manager or object was specified, and that appropriate authority exists.
MQRC2 is licensed under Apache License 2.
Regards,
Roger Lacroix
Capitalware Inc.