MQ

 View Only
  • 1.  Error AMQ 4172

    Posted Fri February 02, 2024 01:21 PM

    I have a couple of MQ test servers that perform as backup for each other and on the secondary server I am trying to start the trigger service and receive an error:

    AMQ4172- just curious what this inidicates?

    Thanks!



    ------------------------------
    Skid Minix
    ------------------------------


  • 2.  RE: Error AMQ 4172

    IBM Champion
    Posted Fri February 02, 2024 03:32 PM

    Hi Skid,

    That's an MQ Explorer error message. Are you using MQ Explorer?

    There is an APAR to fix this error coming out in too many scenarios, APAR IT30603, does it apply to you? (You don't say your MQ Version so I cannot tell myself).

    Cheers,

    Morag



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



  • 3.  RE: Error AMQ 4172

    Posted Mon February 05, 2024 10:48 AM

    Yes I am using MQ Explorer version 9.1.3

    IBM MQ Explorer
    Version: 9.1.3.0

    OS: Windows Server 2012, v.6.2, x86_64 / win32



    ------------------------------
    Skid Minix
    ------------------------------



  • 4.  RE: Error AMQ 4172

    Posted Mon February 05, 2024 11:45 AM

    Is there a way to run this from the command line?



    ------------------------------
    Skid Minix
    ------------------------------



  • 5.  RE: Error AMQ 4172

    IBM Champion
    Posted Tue February 06, 2024 10:22 PM

    Hi Skid,

    You haven't told us a lot about what you are doing so I apologise if my guess here is way off base. In your original post you said, "I am trying to start the trigger service". I am assuming that this is an MQ SERVICE object that runs the trigger monitor program rather like the one described here. If so, then yes, there is a way to start this service from the command line instead of using MQ Explorer.

    To do this, use an MQSC command issuing program, such as runmqsc, and type a command like the following:-

    START SERVICE(TRIGGER.MONITOR)

    where you replace the text "TRIGGER.MONITOR" with whatever name you have used for your SERVICE object.

    If this is not what you are looking for, please reply with more details about what it is that you are doing and need help with to save us guessing further.

    P.S. If you're truly on V9.1.3 then you need to upgrade to an in-support release. V9.1.3 is a CD release and so did not have as long a life-span as LTS releases do, and is well out of support now. The APAR I mentioned was closed in November 2019 had it's fix targeted for V9.1.5, so likely is relevant to you, but that is well old.

    Cheers,
    Morag



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