When auditing is enabled, the system audit journal logs an AD (Change auditing attribute) entry for every object and user profile that has the attribute changed. If you don't capture changes that you want to save, the entries will be gone from the system when the receivers that contain them are deleted. They may be restored when you need to review them, but that's probably not what you're interested in doing. So, you probably will need to run DSPOBJD for each of the libraries and objects in those libraries that you need to cover. Request DETAIL(*BASIC) into an *OUTFILE and query the final result for the values in the ODAUDT field. You might run an initial SELECT ODAUDT FROM qtemp/myobj GROUP BY ODAUDT to see what all of the different values might be. Since that's likely to be a lot of records and since it would get complex enough just coding to get all of the objects that needed to be checked, I would probably use the <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/qgyolobj.htm">Open List of Objects (QGYOLOBJ) API</a> (and the other <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/misc1b.htm">Process Open List APIs</a>), and just grab each value as it came through. User profiles are easier because there are relatively very few of them. DSPUSRPRF to an *OUTFILE is the easy route there. Tom

When auditing is enabled, the system audit journal logs an AD (Change auditing attribute) entry for every object and user profile that has the attribute changed. If you don't capture changes that you want to save, the entries will be gone from the system when the receivers that contain them are deleted. They may be restored when you need to review them, but that's probably not what you're interested in doing. So, you probably will need to run DSPOBJD for each of the libraries and objects in those libraries that you need to cover. Request DETAIL(*BASIC) into an *OUTFILE and query the final result for the values in the ODAUDT field. You might run an initial SELECT ODAUDT FROM qtemp/myobj GROUP BY ODAUDT to see what all of the different values might be. Since that's likely to be a lot of records and since it would get complex enough just coding to get all of the objects that needed to be checked, I would probably use the <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/qgyolobj.htm">Open List of Objects (QGYOLOBJ) API</a> (and the other <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/misc1b.htm">Process Open List APIs</a>), and just grab each value as it came through. User profiles are easier because there are relatively very few of them. DSPUSRPRF to an *OUTFILE is the easy route there. Tom