This document provides information related to using Adabas Fastpath with Adabas Auditing:

• Introduction

• Adabas Requirements

• Auditing Requirements

• Activation

---

Introduction

Adabas Auditing (ALA) allows customers to track who is accessing, reading and changing data in an Adabas database.

Adabas Fastpath direct-access optimization enables Adabas command queries to be satisfied by the client without the need for database access. Therefore, when such optimization is present, a database may not see every access command.

When auditing support is activated for Adabas Fastpath, the Fastpath Asynchronous Buffer Manager (ABM), which is hosted by the Adabas System Coordinator daemon, reads the appropriate ADAANP auditing parameters for each Adabas nucleus which has files defined to Fastpath for direct-access optimization.

Adabas Fastpath applies these same ADAANP parameters when collecting audit data for each direct-access optimized command and forwards the data to the appropriate Audit Server.

Note that Adabas Fastpath only optimizes access commands, so if your implementation of Adabas Auditing is to collect only updates then there is no need to activate auditing support in Adabas Fastpath.

Adabas Requirements

The Adabas System Coordinator should run with the same Adabas version (or later) as that used by the Adabas database(s) whose data is being audited.

Auditing Requirements

Support for Adabas Auditing within Adabas Fastpath is only provided for ALA 2.3 SP2 and above.

Activation

To activate support for Adabas Auditing, set AFP AUDITING=YES in the Adabas System Coordinator daemon runtime parameters for the COR daemon hosting the Fastpath Asynchronous Buffer Manager. For information on this parameter along with other applicable auditing-related parameters, refer to COR Daemon Runtime Parameters.

Additionally, for auditing-related operator commands, refer to Operator Commands.