Activity Logging for an CA ADS Dialog › Overview

Overview

What it Does

The activity logging feature of CA ADS creates activity records that document all potential database activity for a dialog. Documentation is based on the database commands issued explicitly or implicitly by the dialog's processes. (Examples of implicit database commands are the implicit READY command, issued automatically for each subschema area when a run unit is opened for a process, and the BIND command, issued automatically for each subschema record used by the dialog.) If enabled, activity logging is performed when a dialog is compiled and has no impact on runtime performance.

The activity logging feature can be used to perform the following tasks:

• Monitor database usage ── If runtime activity is high for a particular subschema area, set, record, or logical record, activity records can show which dialogs contain database commands that potentially access the entity.
• Modify dictionary entity occurrences ── If a subschema area, set, record, or logical record needs to be modified, activity records can show which dialogs need to be recompiled as a result of the modification.

Enabling Activity Logging

The activity logging feature is enabled or disabled at system generation. The application developer can override the system generation default when defining a dialog.

If enabled, the activity logging feature creates database activity records when a dialog is compiled. Database activity records can be accessed by using query programs such as OnLine Query, by using the Data Dictionary Reporter, or by writing an appropriate program.

The remainder of this appendix describes the data dictionary organization and the format of activity logging records.

More information:

CA ADS Dialog Compiler (ADSC)