×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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?
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
