Return to Home pageContact pageAbout Cosyn SoftwareProduct main pageServices pageWeb-based support pagePartners pageDownload request pageCosyn clients
Cosyn Software
Cosyn Audit Trail for IBM AS/400® & iSeries®
Database Change Logging without Journaling

Download  - No obligation 30 day trial or more information
PDF  - Product overview

Audit Trail/400 delivers cost-effective database change logging for iSeries customers. Tracking database changes may be required to achieve compliance with aspects of Federal or Corporate regulations, or simply for improved control. Often existing ERP applications do not provide audit trails and customers may be faced with major development projects to implement them.

Audit Trail/400 is simple to use and requires no changes to your ERP software. The product uses database triggers to log changes, not journaling. Changes from all sources are logged. So in addition to ERP application user changes, updates from utilities such as Interactive SQL, DFU and DBU are also tracked. Audit Trail/400 gives you, and the auditors, the complete picture.

Sophisticated Management, Inquiry & Reporting

Audit Trail/400 builds powerful inquiry and reporting functions. Reports show you the complete chronology of field value changes. Inquiries allow you to step backwards and forwards through the history on screen, highlighting the changes. In both cases the before and after values are easy to see.

Audit Trail/400 includes API commands to let you incorporate standard reporting and inquiry functions within local programs. Tracked data is output to DB2 UDB/400 physical files and you can use these like any other file on your system. For example you could develop local programs that use the audit logs, or inquire on them using SQL or Query.

5 Easy Steps to Audit Trail Creation

Telling Audit Trail/400 which files and fields to monitor is very simple.

  1. Select the data library from the list of libraries in your library list
  2. Select the physical file to track from the list of files in the data library
  3. Select the control information you want to record. Each tracking transaction can be identified with the user, date, time, and workstation or job from which the change was made. You can also record the application program name or database utility that initiated the change. If your file contains multiple members select one or more to track.
  4. Select a key or keys, for example the product number in a product master file. Audit Trail/400 displays a list of all fields in the record format, highlighting any that have been defined as keys in the physical file definition or any of its logical views.
  5. Select the fields to track. Audit Trail/400 then prompts you to select all or any of the file's remaining data fields for tracking.

Audit Trail/400 then automatically generates and attaches the trigger programs to the file, creates some necessary objects and tracking is underway.

Feature Summary
Application independent
Fast performing
Simple configuration
Menu driven interface to all functionality
Uses standard database functionality - DB2/400 triggers (introduced in OS/400 V3 Release 1)
Triggers only fire if something changes
Data only logged if selected fields affected
Tuned to do the minimum of in-line interactive processing, offloading build processing to a server program
ILE throughout, SAA compliant displays
User chooses which files, controls, keys and fields to audit using simple panels
Hard and soft trigger 'suspend' and 'resume' functions for control during system maintenance
No ERP program changes required so reduces cost of future application software upgrades
If triggers are being used already you can integrate the Audit Trail/400 trigger with your local trigger
If the file layout is changed Audit Trail/400 will automatically detect the changed layout
You can track the program name or database utility that made the change. Identifies the application program name, DFU, Interactive SQL and DDM. Identifies changes made using popular OEM utilities DBU, Surveyor/400 and WRKDBF
API commands available to call from your code or scheduler for inquiry, report, supersede, purge, suspend and resume tracking
Self-managing, optional automatic purging of tracking file data
Data management includes a 'Supersession' function. This lets you segment and 'park' old tracking data, and create a new version of the tracking data file on the fly. After splitting the audit trail data into manageable blocks the older file can be retained for legacy inquiry or deleted when no longer required

System Requirements
OS/400 V4R2M0 or later. Earlier version support available on request.
Final storage requirement depends on the number of files being tracked and how often they are updated. Base system: allow 20Mb
Audit Trail/400's build server automatically creates physical files, as well as output, inquiry and purge programs specific to file being tracked. Standard OS/400 commands CRTBNDRPG, CRTPF and CRTDSPF must be present on your system

Sounds interesting?
Please contact us if you would like more information or a preview.

     About Cosyn

     Inquiry & Download
     Audit Trail/400
     Spool Manager/400

  Support Gateway
     Knowledge Base
     Issues Tracking

     iSeries Development
     Web, Network Dev

  BPCS Enhancements
     Accounts Payable
     Accounts Receivable
     General Ledger
     Order Entry
     Sales Analysis
     Sys. Functions & Usability