× 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 discovered that QAUDJRN type DO (delete object) had references to STMFs
>being deleted but the directory/filename was *N/*N and the user ID was not
>readable.
>
>We're at V4R5 with most QAUDLVL options "on" (not *NETCMN, *OFCSRV,
>*OPTICAL) and *QSECURITY 40.
>
>How can we audit who deletes IFS files?

Steve,

Make sure that QAUDLVL contains *DELETE. It sounds to me like you may be
looking at the wrong fields in the DO audit record. (The object name and
library fields will contain *N when the object is a stream file or
directory.) The complete job name (including the user name) should be
included in the first few characters of each record. There is also a
current user profile field that may be filled in. If you are using DSPJRN
to display the audit record you should press "F10=Display only entry
details" to see the job name.

In V4R5 when a stream file is deleted the name of the file is not placed in
the record, but char(16) file Ids of the file and its parent will be placed
in the directory. But since the object was deleted you will not be able to
use the file Id to get its name. About the only thing you can do is to look
at previous audit records that may contain both the name of the file and
the same field Id.

The DO audit record was enhanced in V5R1 and possibly again in V5R2. It now
included the name and path of the deleted stream file.

Ed Fishel,
edfishel@us.ibm.com




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.