RE: QSYSMSG message queue

Yea, I heard from a LIC developer several years ago something about internal
authorities etc. getting in the way of some messages. That person suggested
(strongly) that I change the owner of that message queue to QSECOFR. As
Mark has suggested QSYS works too, but I never change an object not created
by IBM to be owned by QSYS.

--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jeff
Crosby
Sent: Friday, May 7, 2021 8:25 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: QSYSMSG message queue

As of this morning, CPF1393 shows up in QSYSMSG.


On Thu, May 6, 2021 at 4:14 PM Mark Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> wrote:

Jeff,

On my system, QSYSMSG is owned by QSYS, and CPF1393 dutifully shows up
there. :-)

Mark

On Thursday, May 6, 2021, 3:52:45 PM EDT, Jeff Crosby <

jlcrosby@xxxxxxxxxxxxxxxx> wrote:

In another thread -

Mark wrote:
Create a message queue named QSYSMSG in QSYS. Then in addition to
sending critical messages to QSYSOPR (and QHST) the system will also
send them to QSYSMSG.
It is then easy to write a program to monitor QSYSMSG for certain
errors and "take appropriate action." (CPF1393 does get sent to
QSYSMSG.)

Then Jim wrote:
Good idea but there's an extra step: Change the owner of QSYS/QSYSMSG
to QSECOFR, or create it with QSECOFR.
Incomplete results otherwise.

Interesting. I've had QSYSMSG for as long as I can remember. CPF1393
does not show up there. My QSYSMSG is owned by QPGMR because it was
created by (drum roll) yours truly.

You're saying if I change ownership to QSECOFR, additional messages
will show there?


--


*Jeff Crosby*
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of
my company. Unless I say so.
--
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.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
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.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com