MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2008

RE: Object Auditing Question



fixed

I think I just figured out my own answer. The system value QCRTOBJAUD is
the value newly created objects use, correct? And you can also use this at
a library level using the CHGLIB value of CRTOBJAUD(*usrprf). Am I on the
right track here?

Thanks, Larry

Larry Ketzes | Senior iSeries System Administrator | AIG / ALICO - American
Life Insurance Company
One ALICO Plaza, 600 N. King Street, AMIS | Wilmington, DE 19801 | *:
302.594.2146 | 7: 302.830.4524| *: larry.ketzes@xxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ketzes, Larry
Sent: Wednesday, July 16, 2008 9:37 AM
To: 'Midrange Systems Technical Discussion'
Subject: Object Auditing Question

Hello everyone,
I have a question about activating user auditing for powerful users.
First my assumption:
1) You change the user profile(s) in question with CHGUSRAUD command
to say *all (for all changes) or *change (for changes).

Now, at this point I believe it is recommended you change the files
you want audited with the CHGOBJAUD command. Must I assume this auditing
option is NOT a parameter on the CRTF command and you therefore cannot have
a default value in place for your system files on creation? If this is
correct, then I might think that IBM did this on purpose so that excessive
auditing info is not accumulated.
If this is correct, they can I safely assume that any files that
have auditing turned on had to have them specifically and manually turned
on.

Thanks, Larry


Larry Ketzes | Senior iSeries System Administrator | AIG / ALICO - American
Life Insurance Company
One ALICO Plaza, 600 N. King Street, AMIS | Wilmington, DE 19801 | *:
302.594.2146 | 7: 302.830.4524| *: larry.ketzes@xxxxxxx





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact