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

TMF ARLIB2 Audit-Reading Procedures
HP NonStop TMF Application Programmer’s Guide—522419-005
5-31
Field Descriptions
For entry-sequenced, relative, or unstructured files, the record key field represents the
two-word internal form of the data record address, which is not particularly useful. You
can use the ARGETRECADDR procedure to copy the record address (in external
form) from the audit record into your application buffer when you encounter an update
auditcomp record for one of these file types.
RECTYPE
This field specifies the type of audit record that was read. Table 5-1 shows the
applicable values.
SEQNO
This field specifies the sequence number of the current audit file within the audit-trail.
SEQNO is part of the cursor positioning information.
TIMESTAMP
This is a 4-word Julian timestamp, stored in the audit trail, that represents Greenwich
Mean Time (GMT). If necessary, you are responsible for converting the timestamp to
Local Standard Time (LST) or Local Civil Time (LCT).
When an audit record contains a timestamp, the value returned by the ARREAD
procedure is the Julian value stored in the audit record. Note that many of the audit
records do not contain a timestamp. For such records, TIMESTAMP refers to the
timestamp in the header of the audit block containing the record; that timestamp
indicates when the entire block was written to disk.
Timestamps provide only a coarse means of placing audited events in time. There are
several reasons for this, one of which is the use of block header timestamps, as
previously mentioned. Audit records are stored in a disk process buffer for some
period of time before the block(s) containing them are actually written to disk. This
means that the TIMESTAMP value from the block header will indicate a time that is
later than the time when the record was generated.
Another reason for an irregular time track is that timestamps are based upon the
system time as set by the system operator. It is possible for an operator to set the
system time or date to an incorrect value.
Finally, separate disk processes using independent buffering can all write records to a
single audit trail. This scenario could result in records that have later timestamps
appearing before records that were actually generated earlier by a different disk
process.
TRANSID
The TRANSID is the unique 4-word transaction identifier assigned to the particular
transaction.