Re: QSYSOPR message queue security -- MIDRANGE-L

Subject: Re: QSYSOPR message queue security
From: CRPence <CRPbottle@xxxxxxxxx>
Date: Tue, 12 Mar 2013 09:34:15 -0700
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Not logged to the system. , John Mathew

This mailing list archive is Copyright 1997-2025 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.