Release notes of Adabas Auditing for z/OS.
The documentation for Adabas Auditing's Audit Data Retrieval is only available by request from product support. Contact your nearest Software AG representative for further guidance.
The Audit Log replaces the Command Log in the Audit Server. Refer to the following table for topics concerning the creation and operation of Audit Logs.
| Topic | Description |
|---|---|
| Create Audit Logs | DDALOGRn datasets must be created and formatted. For more information, refer to ADAFRM ALOGFRM. |
| ADARUN parameters | ADARUN parameters must be added to control Audit Log processing. For more information relating to the parameters DUALALD, DUALALS, NALOG, ALOGDEV and ALOGSIZE, refer to Pertinent ADARUN Parameters for Auditing. |
| Force End-of-file | The operator command FEOFAL is used to force end-of-file on the current Audit Log. For more information, refer to FEOFAL Command. |
| Add/Delete Audit Logs | Audit Logs can be added and deleted using the ADADBS utility. For more information, refer to ADADBS ADDALOG and ADADBS DELALOG respectively. |
| Copying Audit Logs | Audit Logs are copied using the ADARES utility. For more information, refer to ADARES ALCOPY. |
In the event of a disconnection between an Auditing Database and an Audit Server, the AUDCONNECT command may be used to re-establish a connection.
For support by an Operator Command, refer to AUDCONNECT Command.
For support by the ADADBS utility, refer to ADADBS OPERCOM AUDCONNECT.
For support by Adabas Auditing Administration Services (SYSALAA), refer to Force Connection Attempt.
When auditing is enabled for a file in an Auditing Database, an Audit Name must be assigned to the file and Adabas will then automatically assign an Audit ID.
In the previous version of Adabas Auditing, the Audit Name used by the utilities ADACMP, ADADBS and ADALOD was incorrectly labelled as AUDITID. This caused confusion between the user assigned Audit Name and the Adabas automatically assigned Audit ID. This has been corrected in Adabas Auditing version 2.2 SP1. The Audit Name used by utilities is now correctly referred to as AUDITNM.
For more information, refer to the following utility documentation:
For ADACMP, refer to ADACMP COMPRESS AUDITNM=
For ADADBS, refer to ADADBS MODFCB AUDITNM=
For ADALOD, refer to ADALOD LOAD Parameters
The DAUDPARM DATABASE function has been added to the DAUDPARM Command issued against an Adabas Nucleus.
For more information, refer to DAUDPARM Command against an Adabas Nucleus.
The operator command DAUDSTAT and the ADADBS OPERCOM DAUDSTAT have been enhanced to report the following information:
The number of items rejected due to errors
The number of admin items
The number of GFFT items
For more information, refer to ADADBS OPERCOM DAUDSTAT.
Additional configuration has been added to enhance the administration of Administration and Structural Database Change (DDL) events:
New Adabas Nucleus Auditing (ADAANP) Database parameters have been added to enable the auditing of database events at the nucleus level. Specified in the ADAANP DD input, the new file parameters are DSERVERID, DADMPARM, DDDLPARM and DOPRPARM.
The FADMPARM, FADMINFO File Auditing parameters have been removed and replaced by the new Database Auditing Parameters.
The Audit Server now requires a DDAUDERR DD card.
For example:
//DDAUDERR DD SYSOUT=X
The majority of messages are written to the console however certain messages will now be written to DDAUDERR.
Messages written to DDAUDERR are formatted similarly to multi-line console messages with the message number and Database ID appearing only on the first line. Each line is prefixed with the Julian date and local time.
Changes to the structure and content of the Audit system file require that a new system file must be loaded into the Audit Server using the ALLSYSF dataset supplied with this version of Adabas Auditing.
For more information on loading an Audit system file, refer to ADALOD LOAD Parameters for the Adabas Audit Server.
Reloading the Audit system file will require the recreation in SYSALA of any configuration you may have defined using the previous version of Adabas Auditing (for example subscriptions, destinations, filters, etc..).
After loading the new Audit system file, the predefined subscriptions SUBSYS1 and SUBSYS2 will require updating, adding a destination, and DBID or DBID/files, to avoid the following warning messages:
ADAAJZ At least one destination is required for subscription SUBSYS1 ADAAJZ At least one destination is required for subscription SUBSYS2
If necessary, they can be assigned to a NULL destination temporarily, as you initially define your Auditing Server environment and update them later with a permanent solution.