Overview

Each user can define a series of user-dependent settings for Adabas Audit Data Retrieval and the Beta Browser. This chapter describes how you can customize these settings to suit your own needs or preferences.

Adabas Audit Data Retrieval profile

Your Adabas Audit Data Retrieval profile includes information on:

• The Adabas Audit Data Retrieval subsystem you work with
• The language and date mask used in panels
• The default jobcard used when generating JCL
• The print characteristics for printing tables (TPRINT)
• Current selection criteria under option 1 (BROWSE)
• The user-defined layout of the List Selection table

The current settings are stored in your user profile when you exit Adabas Audit Data Retrieval and will be restored at your next Adabas Audit Data Retrieval session. Changes to your user profile take effect immediately.

Each Adabas Audit Data Retrieval user (TSO user ID) has his or her own profile.

Browser profile

The Browser profile includes information on how lists are displayed on the screen.

There is one Browser user profile for each user; this is independent of the individual product. For example, if you work with _beta log|z and Adabas Audit Data Retrieval, changing the color of the ruler when browsing a list under _beta log|z will also affect the color of the ruler when browsing lists under Adabas Audit Data Retrieval.

Where is the user profile stored?

When a user works under TSO, the user profile is stored in ISPF variables. When a user works under VDF, the user profile is stored in the VDF database. (When the following description refers to ISPF variables, this is meant to include VDF, which is a simulation of an ISPF environment.)

The following applies to the validity of the user profile:

• Changes to your user profile take effect immediately.
• When an Adabas Audit Data Retrieval session is terminated normally, the settings will also apply to future sessions.

If system works with VCI table

The VCI table contains one record for each user (user definition). This record can be used to initialize some of the settings stored in ISPF variables with predefined values when a user calls Adabas Audit Data Retrieval.

If the VCI table is processed when a user calls Adabas Audit Data Retrieval, the settings stored in the user profile are overwritten with the values from the user definition.

A variable will be overwritten only if the corresponding field in the user record contains a value.

From the user's point of view, this means:

If the user definition contains a setting (for example, that the product language is English), then the user can change the product language for the current session. When the user terminates his Adabas Audit Data Retrieval session and then calls Adabas Audit Data Retrieval again, the settings from the user definition (product language is English) will apply again.

User settings in VCI table

As an administrator, you can use the VCI table to ensure that individual users always find the same default values when calling Adabas Audit Data Retrieval, for example, that the List/Report Selection panel contains certain default values in certain fields.

In addition to this, you can use the VCI table to block certain fields in the List/Report Selection panel or to make these fields required.

When does a system use the VCI table?

When a user works under VDF or under _beta view, the VCI table is always processed.

When a user works under TSO, Adabas Audit Data Retrieval must be called with the initialization exit in order to process the VCI table. For more information, refer to the Adabas Audit Data Retrieval Installation and System Guide.