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



Mark,
The first part helps: DSPOBJAUT QSYSOPR *MSGQ
Object ---------------Data---------------
User Group Authority Read Add Update Delete Execute
*PUBLIC USER DEF X X X
Generally *PUBLIC cannot update nor delete. They can add, which is a good thing.

The second part does nothing: DSPLOG LOG(QHST) PERIOD((1100)) OUTPUT(*PRINT)
I did an F16 and an F13 and nothing appeared here.

None of the STRJRN* family of commands are applicable. I tried this:
STRJRN OBJ(('/QSYS.LIB/QSYSOPR.MSGQ')) JRN('/QSYS.LIB/QAUDJRN.JRN')
This resulted in the message in DSPMSGD RANGE(CPE3440)
STRJRNOBJ does not work with *MSGQ objects.

There are some products related to the $SPENDMONEY command for this.

And while one might hope for the following:
F16 runs CLRMSGQ MSGQ(QSYSOPR) CLEAR(*KEEPUNANS)
R13 runs CLRMSGQ MSGQ(QSYSOPR) CLEAR(*ALL)
It's a false hope. Those command keys do not use the command. I renamed the command temporarily and tried it. If it did, it would be quite easy to use a command exit point program to log that.

If you want to really hack around with TRCJOB you can try.

Or you can open a case with IBM asking the same question you asked this list. They may be a big help. Worst case they give you enough information to make a decent RFE.




Rob Berendt

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.