Home » Products » Surveyor/400 » Audit Logs

Audit Logs

Track any file editing and transfers with Surveyor/400's detailed audit logs

For a specific user (or group of users), you can configure Surveyor/400 to create audit logs (trails) for each of the following events:

  • When database records are edited (added, changed, deleted).
  • When database records are exported (downloaded) from the IBM i.
  • When database records are imported (uploaded) to the IBM i.
  • When SQL statements are executed.
  • When spooled files are exported from the IBM i.

These auditing features are provided in the base package of Surveyor/400 (there are no add-on fees).

Audit Logs for File Editing

Audit entries can be created by Surveyor/400 to log any records which a user adds, changes or deletes through the File Editor. You can choose to perform audit logging to either a Spooled file or a Database file. Audit entries can also be configured to store either field-level or record-level detail.

Auditing options
Record Level Auditing For each record added, changed or deleted: An audit log entry will be created with the complete record image.
Field Level Auditing
(Show all Fields)
For each record added, changed or deleted: An audit log entry will be created for each field (even for the fields that did not change).
Field Level Auditing
(Show only changed Fields)
For each record changed: An audit log entry will be created for each field changed. Additions and deletions will also be logged.

You can specify the name of a database file name/library to store the audit log entries into. Complete details are stored in each log entry:

  • Date of Transaction
  • Time of Transaction
  • User whom performed Transaction
  • Type of auditing
  • File name
  • Library
  • Member
  • Format
  • Type of transaction (add, change, delete)
  • Relative Record Number
  • Value of field or record for transaction
  • Comment

Audit Logs for Database Transfers

If a user has authority to transfer data within Surveyor/400, then an audit log can record details about each transfer that is performed by the user. You can specify the name of a database file name/library to store the transfer audit log entries into. Example of information recorded for each download:

  • Date of Transfer
  • Time of Transfer
  • User whom performed the Transfer
  • Type of Transfer
  • Database file exported
  • Library where database file is located
  • Member in database file
  • Query used to filter records
  • Location/name of destination
  • Completion message

Audit Logs for Spooled File Transfers

If a user has authority to download spooled files within Surveyor/400, then an audit log can record details about each download that is performed by the user. You can specify the name of a database file name/library to store the transfer audit log entries into. Complete details will be logged for each spooled file transfer, including:

  • Date of Transfer
  • Time of Transfer
  • User whom performed Transfer
  • Job
  • Spooled file number
  • Spooled file name
  • Location/name of destination
  • Completion message