The 3000Audit Tool is the first user friendly database auditing product. It may be used to monitor who is updating any Image database record on your HP3000. The 3000Audit Tool will bring your company into compliance with the data auditing requirements of the Sarbanes-Oxley Act . The product uses Image Log files to gather the date, time, user name, before and after values of any dataset you need to audit. The auditing information is reformatted and stored in its own easy-to-access Audit Tool Image database.
The 3000Audit Tool was designed so that it can answer your users questions without the intervention of the IT department. Screens and Reports are provided to allow your users to inquire as to what records have been updated by whom.
One of the advantages of the Audit Tools Image database is your ability to incorporate the data with your report writer into your business processes. For example, by finding the DBPUT records, you can obtain the date a record was added to the data base. This would be useful in such applications as "date work order added", or "supplier was added by user xxxxx". Also, you can use the before/after values stored in the DBUPDATE records to monitor other critical fields. Examples would be "Order ship date was mm/dd/yy and now is mm/dd/yy" or "purchase order price has been changed from 9999.99 to 9999.99".
The 3000Audit Tool is also the first product which will obtain "extra" information to allow you to uniquely identify your records. For example, if a user changes a Purchase Order's date, an Image log file record will contain the Purchase Order Number, original value of the date, and new value of the date. However, because you do not know what "line" of the purchase order was updated, this audit trail record is of dubious value. A table in the 3000Audit Tool allows you to specify what field(s) would help identify the dataset. In our example, the purchase order line number would be read from the database and stored with the audit record.
Frequently Asked Questions regarding Image Logging
Will Image Logging slow down our system? Benchmarks have measured that Image logging requires virtually no overhead. No customers have reported a discernable difference in response time.
Isn't Image Logging difficult to administer? You can begin Image Logging simply by entering 4 MPE commands. You need to add a :log stop and a :log restart to your database capacity change process, and that's all. Because the 3000 Audit Tool is designed for auditing purposes, and not rollforward/rollbackward recovery, the administration is more simple.
What types of changes are required to my application? Absolutely no changes whatsoever. You will 'enable your database(s) for logging', and the HP operating system does the rest. The 3000 Audit Tool Utility program manages the Image log files for you.
Features only available in the 3000Audit Tool:
User friendly reporting - The 3000Audit Tool is the only product that allows your users to do their own inquires. You do not need to know log file numbers, or use "syntax" to access log file information. Screens and reports access a table of user friendly field descriptions to display instead of Image field names.
Gathers and Stores Additional Data - Image logging captures a great deal of information regarding your data base. However, the log files require a substantial amount of selection and manipulation due to their difficult to manage format. For a complete audit trail and to more readily identify the records, it is also important to retrieve additional information from the data base, not stored in the image log file, that is relevant for your application.
Simple Management - The 3000Audit Tool automates image log files management in one simple nightly batch job. The Audit Tool Utility automatically switches to a new Image log file, closes the current Image log file, processes the log and moves all the relevant data to the Audit Tool Image database.
Custom Audit Trail Reports - In addition to the standard screens and reports, the 3000Audit Tool stores the audit trail records in an image data base which is structured for easy retrieval and reporting.
