MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  MQ error on triggering function

    Posted Wed January 12, 2022 12:46 PM
    Trying to learn as much as I can, but we have a user trying to trigger a process to a queue on a windows test server and I see the process in the queue, however it just gets stuck, after viewing the logs on the MQ windows server for the queue manager I see this error for the process:

    AMQ8077W: Entity 'ws_mq_channel@mqtest1t' has insufficient authority to access
    object OASYS_LQ_MIB_REQUEST [queue].

    The user has a triggering job that access the queue, Not sure if it is with the user id they are using to access the trigger??

    Other message:

    EXPLANATION:
    The specified entity is not authorized to access the required object. The
    following requested permissions are unauthorized: chg
    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.


  • 2.  RE: MQ error on triggering function

    Posted Wed January 12, 2022 12:59 PM
    Obviously, the triggered job is running under the account 'ws_mq_channel@mqtest1t'.
    And this account is missing at least the MQ rights 'chg' on the OASYS_LQ_MIB_REQUEST queue.
    So we need to add these rights to this group or one of its groups, then do a REFRESH SECURITY.

    HTH, LMD.

    ------------------------------
    Luc-Michel Demey
    DEMEY CONSULTING
    lmd@demey-consulting.fr
    ------------------------------

    Original Message


  • 3.  RE: MQ error on triggering function

    Posted Fri January 14, 2022 03:16 AM

    The 'chg' authority is for using the ALTER command. It would be unusual to be doing an ALTER QLOCAL command as part of a triggered application. You might do an MQSET, but that would require the 'set' authority.

    Additionally, triggered applications run under the user id of the trigger monitor, which if the trigger monitor is a SERVICE then it is the user ID that started the queue manager, which is in the mqm group. So it would be surprising to see an authority problem. Of course you may have started the trigger monitor in the foreground which trying to get your triggered application to work, so it could be a non-mqm user id? Perhaps you can let us know.

    What led you to this error message being related to the triggering problem? Did it match the time frame? Was the it the triggered queue? Was that user ID the one that was setting up triggering on the queue?

    Could you describe a little more about what you mean by "it just gets stuck"? Perhaps we can help you check a few things to get your triggered application working. There are a few things that all have to be set up correctly in order for triggering to work. It can be a bit tricky.

    Can you show us your queue definition, and your process definition, and how you are starting your trigger monitor? Perhaps we can see what the issue is if you show us that.

    Cheers,
    Morag



    ------------------------------
    Morag Hughson
    MQ Technical Education Specialist
    MQGem Software Limited
    Website: https://www.mqgem.com
    ------------------------------

    Original Message