Re: Who is clearing QSYSOPR -- 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.

Subject: Re: Who is clearing QSYSOPR
From: ~TA~ <tadair@xxxxxxxxxxxxxxxx>
Date: Fri, 14 May 2021 14:21:55 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

Excellent information! Thank you to all who responded.

So, to begin audit journaling on QSYSOPR would the following steps suffice?

1. Include the *OBJAUD value in QAUDCTL.
2. CHGOBJAUD QSYS/QSYSOPR OBJTYPE(*MSGQ) OBJAUD(*CHANGE)

Thanks again.

~TA~

On 5/14/2021 10:10 AM, ~TA~ wrote:

I'm attempting to set up QAUDJRN to determine who is clearing the system operator message queue (QSYSOPR). I've searched the archive, I've searched the internet, and I still can't seem to find a straight-up answer. I would appreciate someone pointing me in the right direction.

We're on 7.3.

Thanks in advance.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Who is clearing QSYSOPR , ~TA~

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.