OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
acct_open() /* first code point */
/* Uses the event number for acct_open(), */
/* evt_vn_bank_server_acct_open */
dce_aud_start(evt_vn_bank_server_acct_open,
binding,options,outcome,&ard, &status);
if (ard) /* If events need to be logged */
dce_aud_put_ev_info(ard,info,&status);
if (ard) /* If events were logged */
dce_aud_commit(at,ard,options,format,&outcome,&status);
acct_close() /* second code point */
/* Uses the event number for acct_close(), */
/* evt_vn_bank_server_acct_close */
dce_aud_start(evt_vn_bank_server_acct_close,
binding,options,outcome,&ard, &status);
if (ard) /* If events need to be logged */
dce_aud_put_ev_info(ard,info,&status);
if (ard) /* If events were logged */
dce_aud_commit(at,ard,options,format,&outcome,&status);
5. Closes the audit trail file when the server shuts down, using the
dce_aud_close() API in the main server routine. For example:
dce_aud_close(audit_trail, &status);
42.4.2 Administrator Tasks
The administrator uses the event numbers representing the different code points in the
audit client application server program to create event class files and filter guides in the
following manner:
1. The administrator obtains the event numbers of the code points (representing each
audit event) from the application server programmer. In our example, these code
points were assigned the following event numbers:
acct_open( ) 0x01000000
acct_close() 0x01000001
acct_withdraw() 0x01000002
acct_deposit( ) 0x01000003
acct_transfer() 0x01000004
(Note that event numbers should be entirely sequential. That is, no missing
members of the sequence are allowed.)
42 − 12 Tandem Computers Incorporated 124243