QSYSOPR message queue security -- MIDRANGE-L

× 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.

And in your CL, you could also DSPMSGQ QSYSOPR *PRINT.
I like to do that as part of the Shift Change / Daily Startup.
It is nice to have the report around for about a week,
because it sure beats looking at DSPLOG.

Just curious... Is the output from DSPLOG really that much different
than DSPMSG OUTPUT(*PRINT)? The DSPLOG also has an OUTPUT(*PRINT), if
the comparison was being made between spooled DSPMSG and an interactive
display for presentation of DSPLOG output. But even better IMO, the
DSPLOG has OUTPUT(*PRTSECLVL) to include the second level message
details, which AFaIK, the DSPMSG command still does not have.

I am not sure, but I think there is more system stuff in DSPLOG than in QSYSOPR. At least, that been my experience.
And QSYSOPR can be cleaned up / individual lines deleted by using F11.
And a utility like bytware's MPLUS Message Monitor can remove messages as it monitors the Message-Queue.

Also, programmers can have their programs send INQUIRY messages using SNDPGMMSG and other types to QSYSOPR.

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.