TMF Application Programmer's Guide (G06.24+)

TMF ARLIB2 Audit-Reading Procedures
HP NonStop TMF Application Programmer’s Guide—522419-004
5-2
ARLIB2 Compared to ARLIB
Once TMF audit-reading procedures are bound into your program, you can use them
to open an audit-trail file and read individual records from that file. Rather than return
entire audit records, the procedures return only those fields that contain information
useful to you from only those records useful to you. Fields and records that are only of
use to TMF are not accessible. By ignoring such information, the procedures make it
less likely that future changes to the format of TMF audit trails will adversely affect your
audit-reading programs.
TMF audit-reading procedures do no filtering or analysis; they simply provide selected
information from each accessible audit record. If you want any filtering, analysis, or
correlation of the returned data, your program must do it.
Audit records do not include a user ID or a terminal name. You can incorporate this
type of information into an audit trail, however, by having your application write a
record to an audited security log file after each BEGINTRANSACTION process; this
would insert an accessible audit record into the audit trail. The format and content of
such records could be customized to your specific application. To conserve disk
space, you could then delete the security record immediately from the audited security
log file.
ARLIB2 Compared to ARLIB
The ARLIB2 audit-reading procedures read audit records for SQL/MX objects as well
as for Enscribe and SQL/MP objects. The ARLIB audit-reading procedures read audit
records only for Enscribe and SQL/MP objects.
The changes necessary to support SQL/MX objects are significant, including several
new procedures and changes to many of the record formats. Programs bound with
previous RVUs of ARLIB must not be used on systems that use SQL/MX objects.
Such programs must be rebound with a current version of ARLIB, or they must be
changed to use ARLIB2.
ARLIB2 is a native object file. To use this product, existing programs must be changed
to use the native compiler for their language and to link with NLD. The PASCAL
compiler cannot generate native code, however, so ARLIB2 is not usable by programs
written in PASCAL.
To read and process audit records for SQL/MX objects, you use combinations of the
following ARLIB2 procedures:
ARGETMXCOLUMNINFO
Returns column-format information for the SQL/MX object indicated by the
current audit record.
ARFETCHMXBEFOREDATA
Copies the before-image field from an SQL/MX audit record to the application
buffer (uses bit maps).