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



Tim,
(and for the archives ...)
If you issue EDTOBJAUT QSYSOPR *MSGQ
then remove the "X" from the "Delete" column in the row for "QPGMR" ...
The F-keys still appear on the DSPMSG panel, but if you press them, you get a message that says:
    CPD2419 Not authorized to delete messages.
:D
Mark S. Waterbury


On Monday, May 17, 2021, 4:30:38 PM EDT, ~TA~ <tadair@xxxxxxxxxxxxxxxx> wrote:

I had thought about that.  I'm testing with my own user profile, and
it's set to *BASIC (for DSPMSG QSYSOPR) on all our systems.

Thanks.

~TA~


On 5/17/2021 2:59 PM, Mark Waterbury wrote:
  Tim,
Could it be whether the user profile (*USRPRF) has ASTLVL set to *INTERMED or *ADVANCED vs. *BASIC?
Mark

      On Monday, May 17, 2021, 3:56:39 PM EDT, ~TA~ <tadair@xxxxxxxxxxxxxxxx> wrote:
 
  The solution may be even simpler.  The problem seems to be that when a
user displays the system operator message queue (QSYSOPR), one of the
function keys at bottom is "F16=Remove messages not needing a reply".
Now, here's the kicker - we have around 20 IBM i systems, and some of
them have the F16 option, and some do not.  They're all at 7.3 so that
isn't the issue.  There's no correlation with the SECLVL, so that isn't
it.  It doesn't seem to matter which user profile is used, so that isn't it.

I checked the OBJAUT of QSYS/QSYSOPR OBJTYPE(*MSGQ) and it's the same
across our systems, so that isn't it.

If I can 'turn off' the F16 option on all systems, the problem is solved.

I would very much appreciate your thoughts on this.  I couldn't find
anything in the archive, and Google wasn't any help.

Thank you in advance.

~TA~



On 5/14/2021 2:21 PM, ~TA~ wrote:
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.