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



We are trying to use the system's security auditing to track when
objects in several production libraries are created, changed or deleted.
We used the CHGSECAUD command to start the journaling. For the QAUDCTL
parameter we used *AUDLVL and *NOQTEMP. For the QAUDLVL parameter we
used *CREATE, *DELETE & *OBJMGT.

The journal contains way more information then we need. Objects in
development libraries are in the journal as well as faxing entries and
other information we do not need. We would like to audit only certain
libraries. We tried using the *OBJAUD value for QAUDCTL and used
CHGOBJAUD to turn on auditing for a few objects. This looks like it is
close to what we need, but we ran into a few issues that raised some
questions and we were wondering how other people audit their systems.

1. Is there a way to audit a few libraries? Would using the CHGOBJAUD
command for a library audit all objects in that library? What about
when new objects are created?

2. Would we have to run the CHGOBJAUD command over all objects in a
library to limit which libraries we want to audit? How do you track
when a new object is created since the object doesn't have the auditing
flag set on?

3. Is there a way to audit when a Query/400 is changed, created or
deleted? We didn't seem to be able to see any entries for queries.

Any help or ideas on how to audit objects on your system would be
greatly appreciated. I am aware there are auditing packages available.
We can read the journal ourselves and produce the reports we need. It
is just a matter of limiting what is in the journal.

Thanks,
Kent

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.