RE: QAUDJRN DI - Directory services

Respectfully,
Michael Mayer
IBM i on Power System Admin
ERMCO-ECI
2225 Industrial Rd
Dyersburg, Tennessee 38024
Office and OnCall: 731.676.4318
Cell: 518.641.8906
Email: michael.mayer@xxxxxxxxxxxxx<mailto:michael.mayer@xxxxxxxxxxxxx>
https://www.ermco-eci.com<https://www.ermco-eci.com/>
IBM i Personal Blog: https://ibmireference.blogspot.com<https://ibmireference.blogspot.com/>
"Success is not final. Failure is not fatal. It is the courage to continue that counts".


[cid:image001.gif@01D976B7.9DFA2750]





From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob via MIDRANGE-L
Sent: Monday, April 24, 2023 2:11 PM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: qpgmr400@xxxxxxxxxxxxxxx
Subject: RE: QAUDJRN DI - Directory services

Look at table 133 ("Security auditing journal entries") in the security
reference manual.

https://www.ibm.com/docs/en/ssw_ibm_i_75/pdf/sc415302.pdf<https://www.ibm.com/docs/en/ssw_ibm_i_75/pdf/sc415302.pdf>

The following QAUDLVL values can result in T/DI Journal entries.

*AUTFAIL
*CREATE
*DELETE
*OBJMGT
*SECDIRSRV
*SECURITY
*SYSMGT

plus Object Auditing values *CHANGE and *ALL.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of Justin
Taylor
Sent: Monday, April 24, 2023 9:49 AM
To: MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: QAUDJRN DI - Directory services

Does anyone know which QAUDLVL value controls these QAUDJRN entries?
Code . . . . . . . . : T - Audit trail entry
Type . . . . . . . . : DI - Directory services

I don't see "Directory services" list on this IBM page, and there are
multiple DI entries.
https://www.ibm.com/docs/en/i/7.5?topic=actions-security-auditing-journal-en<https://www.ibm.com/docs/en/i/7.5?topic=actions-security-auditing-journal-en>
tries


TIA
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.

.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<https://archive.midrange.com/midrange-l>.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.


The information in this email may be confidential. It is intended only for the person(s) named above. If you are not the intended recipient, please notify the sender and do not review, distribute, or duplicate this email.