<div>
We do journal our files. &nbsp;Are you saying that even using ODBC, the iSeries OS will journalize who the user was, what file he/she accessed, and assuming the before/after images are available, that the journals would capture any changes made through ODBC? &nbsp;That would be fantastic and seemingly answer any auditor's concern.
</div>


<div>
<br />
That's absolutely correct. Journaling logs all the changes and who made them.<br />
<br />
-- DaveSlash
</div>


<div>
This is all hypothetical because we don't usually have users setting up their ODBC connections where they are allowed to update data on the iSeries, just read. &nbsp;However, this doesn't mean someone out there did not configure their ODBC parameters to prevent updates. &nbsp;Just that we've never bothered looking in the journals for any possible ODBC originated updates. &nbsp;I guess we'll start looking for any journal records with strange job names.<br />
<br />
Thanks much and I will accept your answer. &nbsp;Wish there was something quicker and easier inherent to the iSeries and ODBC to use than journals, i.e. some special log file, but your answer makes sense and falls in line with a uniform method for tracking file access. &nbsp;Thanks again!
</div>


<div>
<br />
There are other options, but they're more complex and some of them even cost extra money. I prefer &quot;native&quot; and &quot;cheap&quot; solutions.<br />
<br />
I usually do a DspJrn to an outfile and query the resulting table. It makes the data easier to manage than scrolling through pages and pages of stuff on the green-screen.<br />
<br />
-- DaveSlash<br />

</div>


<div>
I agree Dave. &nbsp;We just got hit with an audit and the journals - once enabled - proved to be a blessing. &nbsp;I had to quickly learn DSPJRN and how to query the outfiles. &nbsp;Funny thing is, I used MS Access to then create an application to report and create file extracts for the users and auditors. &nbsp;I should check the journals for my own ODBC access! &nbsp;LOL!<br />
<br />
I think the company did purchase some third-party software that also monitors file access, but I'm not familiar with it. &nbsp;I did mention this to the person asking but she was looking for a quick answer. &nbsp;You guys on Experts Exchange are about as quick as an answer I could hope for. &nbsp;Just hope this person buys into the answer! &nbsp;:-)<br />
<br />
Thanks again Dave.
</div>


<div>
<div class="content wysiwyg-content">
If a user connected to the IBM iSeries via the IBM Client Access ODBC and linked to a file, is there a way to <br />
<br />
1) know who viewed which files?<br />
2) know if they changed any data and which files/fields?<br />
<br />
Thanks!
</div>
</div>


If a user connected to the IBM iSeries via the IBM Client Access ODBC and linked to a file, is there a way to 

1) know who viewed which files?
2) know if they changed any data and which files/fields?

Thanks!

Is there a way to track what was viewed or changed via ODBC?

IBM i, formerly known as AS/400, is a proprietary, midrange, object-based operating and application system. It includes a relational database, a menu-driven interface, support for multiple users, block-oriented terminal support and printers, and supports security, communications, and web-based application servers including Websphere, Apache and Tomcat.

IBM System i

Operating system security (OS security) is the process of ensuring OS integrity, confidentiality and availability. OS security refers to specified steps or measures used to protect the OS from threats, viruses, worms, malware or remote hacker intrusions. OS security encompasses all preventive-control techniques, which safeguard any computer assets capable of being stolen, edited or deleted if OS security is compromised, including authentication, passwords and threats to systems and programs.