FAQs
Real-Time Program Audit Frequently Asked Questions
Will RTPA affect the production code?
No. When RTPA is installed it creates two new libraries, separate from production: (1) ZZAUDIT, the RTPA object (executable) programs; and (2) an empty, temporary work library (ZZAUDITE) to contain any RTPA activity, including source programs and the expanded objects. These two libraries are used separately from the production system and are designed to be kept entirely separate from the production system. This is standard practice for test vs production environments.
What are the system requirements to use RTPA?
- IBM i Power 5 or later, and appropriate IBM ILE Compilers (RPG, CL, COBOL)
- Approximately 300 million bytes of disk storage
What programming languages does RTPA run in?
The current RTPA product produces audit logs for RTPA for IBM i RPG, IBM I COBOL, and CL. However, the RTPA program is patented for every computer language, and we are working to develop in other languages.
Do I need to expand all my source programs?
No, only the selected programs. Each source program that you want to audit must be expanded with the RTPA program. Only expanded programs will produce audit files.
Will RTPA exceed maximum file limits?
No, there is no number of files limit for the ILE compilers.
Does RTPA for audit all RPG, COBOL, and CL programs?
As far as tested, RTPA audits all RPG IV, COBOL, and CL programs. RPG III programs are automatically converted to RPG IV.
How does RTPA work?
RTPA is a pre-compiler that converts a normal source program into an audit-enabled source program, which is then compiled normally. (Similar to the SQL pre-compiler). The RTPA process is simple:
- RTPA analyzes the source code and then creates a new temporary source code file containing both the source code and audit statements.
- RTPA compiles the audit-enabled source code with the regular compiler. The resulting object is an audit-enabled object program.
- When the audit-enabled program is initiated (interactive or batch), the executable itself produces an audit output file, which we normally refer to as an audit file, or audit.
- The audit file can be viewed in real time as the program executes, or as it is a normal spooled file, printed out after execution. It can also be displayed online, making it searchable.
What types of output does RTPA provide?
RTPA produces three types of outputs: (1) the RTPA audit log, (2) source program documentation, and (3) customized/ad hoc reports produced from the disc audit log file.
The RTPA Audit Log
The RTPA audit log is automatically generated by RTPA. It is produced from the expanded source program, which includes the executing source statement, the moment-in-time the source statement was executed, and the value of the fields in the executing source statements, and more).
The audit log is saved to either a printer spool file (ZZAUDITP) or a DB2 Disk file (ZZAUDITD):
(a) The printer file (printer spool file): for everyday use by programmers
(b) The DB2 disk file (ZZAUDITD): for specialized analysis (eg, for SQL use, the IBM query program, the RTPA query program)
Source program documentation
Documentation only option, inserts comment statements. Useful for the first day analysis to make the entire library more understandable.
Customized/Ad Hoc Reports from the Disc Audit Log File
- If written to disc (option b), various programs (eg, IBM query, SQL, or RTPA Query) can be used to extract and analyze data, including creating and printing reports.
- RTPA Query includes six built-in analytical report options: display files, reports, fields, files, call programs, and programs executed. These show what actually is/has been executed for that job in the RTPA audit log.
- Using SQL or IBM Query allows for the analysis of any field/conditions in the RTPA audit log database, showing what is/has been executed in the RTPA audit log for that job.