
HPMA Audit Message Reference
Table 1: Data Types (cont.)
| Type | Description | 
| 
 | 
 | 
| IP32 | IP Address; a  | 
| 
 | 
 | 
| CSTR | C String; a variable length array of characters. | 
| 
 | 
 | 
Event-Specific  Data
Following the opening “[AUDT” container that identifies the message itself, is a series of items specific to each event or action. Chapter 3, “Message Reference” on page 11 lists attributes commonly used for tracing grid activity.
Common Elements
After the 
Table 2: Common Elements of Audit Messages
| Code | Type | Description | 
| 
 | 
 | 
 | 
| AVER | UI32 | |
| 
 | 
 | Archive software evolves, new versions of services may incorporate | 
| 
 | 
 | new features in audit reporting. This field enables backward com- | 
| 
 | 
 | patibility in the AMS to process messages from older versions of | 
| 
 | 
 | services. | 
| 
 | 
 | 
 | 
| ATYP | FC32 | Event  | 
| 
 | 
 | This governs the “payload” content of the  | 
| 
 | 
 | included. | 
| 
 | 
 | 
 | 
| ATIM | UI64 | |
| 
 | 
 | audit message, measured in microseconds since the operating sys- | 
| 
 | 
 | tem epoch (00:00:00 UTC on 1 January, 1970). Note that most avail- | 
| 
 | 
 | able tools for converting the timestamp to local date and time are | 
| 
 | 
 | based on milliseconds. Rounding or truncation of the database | 
| 
 | 
 | timestamp may be required. | 
| 
 | 
 | 
 | 
| ATID | UI64 | Trace  | 
| 
 | 
 | were triggered by a single event. | 
| 
 | 
 | 
 | 
8
HP Medical Archive