Re: QAUDJRN

Le 03/05/2022 à 21:17, Greg Wilburn a écrit :

So I'm ready to turn this thing off... Actually, I already have.

I changed QAUDCTL to *NONE, but because my QAUDJRN was setup with MNGRCV(*SYSTEM) it creates a new receiver each morning when we IPL.

That's the normal behavior of journal management. You should only see entries related to journal and receivers management, such as new receiver created and attached, previous receiver detached, journal and receivers backed up... This cannot use a lot of disk space. If you specify DLTRCV(*YES) for AUDJRN journal, you will have only one receiver in the chain, even if it is not really a recommended setup for QAUDJRN journal. If you do no longer want to use audit (well, this is not really recommended nowadays) and do not want to manage the journal, you can delete it then delete the receivers.

BUT, according to IBM there shouldn’t be anything in the receiver file. There are definitely ZC entries.

Unless I am wrong, ZC/ZR entries come with QAUDCTL system value set with *OBJAUD. So that is quite strange if they are still here when QAUDCTL is set to *NONE. Are you sure that those ZC entries are *after* QAUDCTL was set to *NONE?

I'm so frustrated right now... why would IBM give you something that has the potential to EAT DISK SPACE at an alarming rate, yet not provide any "cleanup" tools that aren't supplied "AS-IS". Yet we are supposed to turn this on??

Audit journal needs to be properly managed. Normally, you may want to backup then delete the receivers and keep the backup long enough to comply with security rules which require the ability to analyse them in case of security failure. If you do not want to create tools for that, I suggest you to look at some commercial software. Security becomes more and more a key topic nowadays.

FWIW, the DB2 Web Query folks came back and said to turn off auditing on the directory (and subtree) that is generating 99.7% of the AF entries.

As far as I know, you cannot do that. There is no directory or file or object attribute which prevents Authority Failures entries in audit journal. As soon as QAUDLVL(2) system value includes *AUTFAIL, the system will log *all* authority failures. This will always be a matter for security administrator to solve them with setting up appropriate authority. My 2 cents.

Is this really worth all the effort?