System and Audit Reporting

System and audit reporting from HelpSystems

System and Audit Reporting

Simplify IBM i reporting and ease the auditing experience with tools that automatically maintain audit trails and event logs for essential audit data.

Access data that is not in QHST, including critical application info.

Maintain audit trails automatically and receive notification of exceptions.

Readily prove compliance with clear documentation and easy reports.

The Difficulties of Manual System and Audit Reporting

Sorting through QHST entries manually is nearly impossible

If you’ve spent any time in the QHST history log, you might be thinking that they couldn’t pay you enough to mess around in that mine field. Completely understandable.

QHST is essentially an audit trail for activities happening on your IBM i. You can view QHST log entries for things like subsystems starting or ending, see what was saved during a recent backup and what failed, or track when a job was submitted, when it ran, and whether it completed. The system collects these log file entries automatically and they cannot be changed.

While QHST contains a ton of information, each individual entry is skeletal and disconnected from the others. What’s worse, QHST log file entries cannot be queried like information in a database file.

Trying to piece together a summary of your processing for any given day manually is incredibly complex and time consuming. As an alternative, you may have tried to cobble together a command line program (CLP) that would bring QHST data into a database and combine related entries before attempting to interpret the results. Either way, you will never get a complete picture from QHST for the simple reason that QHST doesn’t take your business logic into account.

Over the long-term, supporting in-house CL programs as your business needs or features in the operating system change will be expensive, both in terms of money and man-hours. Not meeting business rules or service-level agreements, whether contracted or implied, can also incur penalty fees or result in loss of business due to downtime.

The bottom line? System and audit reporting is messy. The information exists, it’s just fragmented across a bunch of different logs and message queues. However, reporting is an essential yet easily neglected part of your job, so it’s important to make the process easy so it doesn’t slow you down. The good news? You can enter your specific business rules and audit requirements into system and audit reporting automation software to create a complete audit trail and simplify system and audit reporting.

“We can really satisfy auditor demands. For example, I think the Good Morning Report is worth a million bucks. You come in, you look at it, and you can know what ran normally and what didn’t. Auditors like that.”

Harry Ramsey
Manager of Software Application Development
Pennsylvania Housing Finance Agency

Why Automated System and Audit Reporting Is Essential

Robot software automatically keeps an audit trail and makes audit reporting easy

First, you are both the audited and the auditor of your own operations. In either case, you want to have an ironclad audit trail ready to report. Second, you seek the truth. Being aware of your current operations allows you to see problem areas and make smart changes that can support business growth. We call that IT Operations Analytics or ITOA.

Reporting can quickly become busywork if you can’t access the information you want in order to tell the story you need. With sophisticated automation software, your team can take advantage of built-in reporting or use an external query tool to produce the evidence auditors require.

Automation software with built-in system and audit reporting functionality can also present all your system and audit trail information in a user-friendly interface, making it easy for you to see where your operations stand today so you will know where to make changes to support business growth and new regulations in the future.

Robot Simplifies System and Audit Reporting

  Robot Schedule Robot Console Robot Space Robot Save
Platform IBM i, Windows, UNIX/AIX, Linux IBM i IBM i IBM i
Key Audit Activities
  • Keep audit trail of job changes
  • Pull batch process statistics
  • Report on file events
  • Monitor and report on SLAs
  • Connect messages with replies
  • Keep history of QSYSOPR and QHST events
  • Create database of log information
  • Summarize level of message automation and system resource management
  • Report on disk, memory, and WRKSYSSTS performance values
  • Track object growth
  • Identify disk usage by owner
  • Report on largest libraries
  • Create up-to-date restoration plan
  • Keep audit trail of what was saved, where it was saved, and when
  • Identify objects that were not saved due to locks
  Learn more > Learn more > Learn more > Learn more >

Let's Talk About How We Can Help