Enables Auditing for CONNX for ADABAS

AUDIT = 1

 

When auditing is enabled, any query access against one of the configured audit files will result in an audit record being generated and placed into the audit table.
If auditing is enabled the following configuration settings should also be configured:

 

AUDITDBID - the Adabas Database ID that contains the audit file.

AUDITFILECOUNT - the number of files to be audited

AUDITFILEID - the file number of the Audit file

AUDITPASSWORD - the ADASCR password for writing data to the audit file

AUDITFILTER### - where ### is 001 through 999 - the filter specification that will identify which adabas file to be audited, along with the optional key field.

 

The target audit file has two supported formats - depending on the setting AUDITFORMAT:

If AUDITFORMAT is zero (the default value) then the audit file must have the following structure:

AA - 7,P - Natural timestamp - the time of the audit event

AB - 8.A - UserID - the user identifier

AC - 4,F - The database number for the table that triggered the audit record

AD - 4,F - The file number for the table that triggered the audit record

AE - 4,F - The ISN of the record that triggered the audit.

AF - 100,A - The optional key field from the record that triggered the audit

 

For example, the audit file can be created using the following SQL statement:

create table  AuditFile( AuditTime timestamp NOT NULL, Userid char(8)  NOT NULL, databasenumber integer  NOT NULL, filenumber integer  NOT NULL, ISN integer  NOT NULL, keyfield varchar(100)  NOT NULL)

 

 

If the AUDITFORMAT is 1, then the audit file contains a periodic group and must have the following structure:

1,AA - 7,P - Natural timestamp - the time of the audit event

1,AB - 8.A - UserID - the user identifier

1,AC - 4,F - The database number for the table that triggered the audit record

1,AD - 4,F - The file number for the table that triggered the audit record

1,AE, PE - Periodic group use for audit performance

2,AF - 4,F - The ISN of the record that triggered the audit.

2,AG - 100,A - The optional key field from the record that triggered the audit

 

For example, the audit file can be created using the following SQL statement:

 

Create cluster description adalocal.auditfilenewcluster

FILE NUMBER <your adabas file number> (

create table AuditFileNew(

internalisn seqno(0) not null,

AuditTime timestamp shortname 'AA' NOT NULL  ,

Userid     shortname 'AB' NOT NULL,

databasenumber integer  NOT NULL  shortname 'AC',

filenumber integer  NOT NULL  shortname 'AD',

primary key (internalisn)),

create table  AuditFileNewValueData(

internalisn seqno(0) not null,  

COL_SEQNO_1 SEQNO(1) NOT NULL,

ISN   shortname 'AF' NOT NULL,

keyfield varchar(100)  NOT NULL  shortname 'AG',

foreign key (internalisn) references AuditFileNew,

primary key (internalisn, COL_SEQNO_1))

)

 

AUDITFORMAT = 0 results in a single adabas record for each audit record, which is a simpler format, easier to read, but results in slower performance.

AUDITFORMAT = 1 will store multiple audit records in the periodic group element of a single adabas record.  This results in much better performance, but can make the data a little more difficult to read.

 

 

Default = 0.

 

Environments: Server

Configuration Manager: CONNX Settings; Current Key = CONNX/ADABAS; Key Value/Value Name =  AUDIT

 

Unix Environment Variable: AUDIT

VMS Logical: AUDIT

Started Task: AUDIT

CICS:  AUDIT