MQ

I have a local queue that is a trigger queue and for some reason it can only handle one message at a time, so I changed the triggering type from first to every in MQ Explorer and that seems to have corrected the issue, however once I run a another test it changes the attribute back to first for the type. Is this normal or is there a way to make that parameter stay constant for that queue to alleviate the problem.

Thanks.

I have also set it up using mqsc commands, but get the same results.

This looks to me like a feature of the program processing the queue.
You should make sure that the program does the following

• Opens the queue and does a get with wait
• gets all messages and processes them before closing the queue
• If you need parallel processing, can you use multi-threading in the processing program with a reasonable limit on max # of threads?
• Beware of OS limits or overwhelming the OS when trigger every and having a deep queue.

​

------------------------------
Francois Brandelik
------------------------------

Original Message:
Sent: Fri March 11, 2022 01:26 PM
From: Skid Minix
Subject: MQ triggering property

I have also set it up using mqsc commands, but get the same results.

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

Original Message:
Sent: Fri March 11, 2022 09:47 AM
From: Skid Minix
Subject: MQ triggering property

I have a local queue that is a trigger queue and for some reason it can only handle one message at a time, so I changed the triggering type from first to every in MQ Explorer and that seems to have corrected the issue, however once I run a another test it changes the attribute back to first for the type. Is this normal or is there a way to make that parameter stay constant for that queue to alleviate the problem.

Thanks.

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

Is your Queue Manager in a container?

------------------------------
Bob Gibson
Advisory Software Engineer
IBM
(919) 543-7280
------------------------------

Original Message:
Sent: Fri March 11, 2022 09:47 AM
From: Skid Minix
Subject: MQ triggering property

I have a local queue that is a trigger queue and for some reason it can only handle one message at a time, so I changed the triggering type from first to every in MQ Explorer and that seems to have corrected the issue, however once I run a another test it changes the attribute back to first for the type. Is this normal or is there a way to make that parameter stay constant for that queue to alleviate the problem.

Thanks.

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

As far as I know it is not running in a container.

Is there a way in MQ to run the mqsc commands in some type of script so the trigger type always has the EVERY parameter set? Sort of like in Task Schedular?

You can try to turn on MQ config events to see when and who changed the Trigtype from every back to first. SupportPac MH05 can help to display the Event message.

------------------------------
Kwok Tai Yung
------------------------------

Original Message:
Sent: Fri March 11, 2022 09:47 AM
From: Skid Minix
Subject: MQ triggering property

I have a local queue that is a trigger queue and for some reason it can only handle one message at a time, so I changed the triggering type from first to every in MQ Explorer and that seems to have corrected the issue, however once I run a another test it changes the attribute back to first for the type. Is this normal or is there a way to make that parameter stay constant for that queue to alleviate the problem.

Thanks.

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