On 12 Mar 2013 09:34, CRPence wrote:
On 12 Mar 2013 08:02, Voris, John wrote:
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
Also, programmers can have their programs send INQUIRY messages
using SNDPGMMSG and other types to QSYSOPR.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact