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

TMF ARLIB2 Audit-Reading Procedures
HP NonStop TMF Application Programmer’s Guide522419-004
5-3
Cursors
ARFETCHMXBEFOREDATA2
Copies the before-image field from an SQL/MX audit record to the application
buffer (uses byte maps).
ARFETCHMXAFTERDATA
Copies the after-image field from an SQL/MX audit record to the application
buffer (uses bit maps).
ARFETCHMXAFTERDATA2
Copies the after-image field from an SQL/MX audit record to the application
buffer (uses byte maps).
The structure of the ARRECORD for ARLIB2 differs from the structure for ARLIB, as
follows:
A field has been added to identify audit records for SQL/MX objects.
The rba field used to return the location of the audit record in the audit file has
been expanded from 32 to 64 bits.
The before-image and after-image length fields have been expanded from 16 to 32
bits.
Most of the fields have been reordered to allow for better performance.
Cursors
A cursor provides a reference into an audit trail. Each cursor reflects the generic name
of an audit trail, the sequence number of the file in the trail, the relative byte address
(RBA) of a record in the file, and the direction in which the cursor is to move through
the file (forward or reverse).
Cursor Declaration
You declare a cursor by using the AROPEN procedure. Each AROPEN call passes
the generic name of the desired audit trail and returns a cursor number that you use for
future references to that cursor. You can only open audit trails on the local node. Until
released by a call to the ARCLOSE procedure, each cursor continues to refer to the
specified audit trail. You can have up to 30 cursors declared simultaneously, any
number of which can refer to the same audit trail.
Cursor Positioning
You declare the location and direction of a cursor by using the ARPOSITION
procedure. Each ARPOSITION call supplies the cursor number, the sequence number
of the audit-trail file, an initial byte offset into the file, and the direction in which the
cursor is to move for successive reads. If the supplied offset is not at the beginning of
a record recognized by the audit-reading interface, then the first recognized record in