Re: Qsysopr message queue locks

I don't understand your statement about not locking QSYSOPR.

We have a never-ending batch job that performs the following statement at
the start:

CHGMSGQ MSGQ(QSYSOPR) DLVRY(*BREAK) PGM(MSG_GET *ALWRPY)

This will create an exclusive lock on the message queue!

Any message that is sent to QSYSOPR will kick off the MSG_GET program. It
does a RCVMSG and any message with a severity greater than 40 will send an
email to our Jira system and create a Help Desk ticket.

The only downside is that I can't delete a message from QSYSOPR if for some
reason I wanted to, but that's not a bad thing anyway.

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Cell: (416) 317-3144




On Thu, 11 Sept 2025 at 07:32, Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Yes, and DO NOT lock QSYSOPR ( or QSYSMSG for that matter) since really
bad things could happen if the OS and other things cannot get to that
queue.


Jim Oberholtzer
Agile Technology Architects

On Sep 11, 2025, at 6:22 AM, Rich Loeber <rich@xxxxxxxxx> wrote:

Take a look at the STRWCH command in the OS.

Rich Loeber
Kisco Systems

Rich
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of

Don Brown via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>

Sent: Thursday, September 11, 2025 4:41:47 AM
To: 'Midrange Systems Technical Discussion' <

midrange-l@xxxxxxxxxxxxxxxxxx>

Cc: Don Brown <dbrown@xxxxxxxxxxxxxxxx>
Subject: Qsysopr message queue locks

Hi,

I was using a rcvmsg on the qsysopr message queue with a wait(*max) to

check for a specific message about a locked net server profile.

This message does not go to the qsysmsg queue.

While my monitor program was working fine it did put an exclusive lock

on the message queue.

The application they use has a process that also need to check something

on the qsysopr message queue and failed because my monitor was locking the
queue.

I changed my program to use a specific wait value of 5 seconds and the

put a delay job of 2 minutes if there were no messages received on the
rcvmsg. When the delay job is in effect the lck on the message queue is
released. However, the application provider is still complaining.

My question, is there any other way to monitor messages being added to

the qsysopr message queue that does not put an *EXCL lock on the message
queue ?

Thanks for any suggestions

Cheers

Don


Brisbane - Sydney - Melbourne


Don Brown

Senior Consultant




P: 1300 088 400




DISCLAIMER. Before opening any attachments, check them for viruses and

defects. This email and its attachments may contain confidential
information. If you are not the intended recipient, please do not read,
distribute or copy this email or its attachments but notify sender and
delete it. Any views expressed in this email are those of the individual
sender

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.