Certain definition must be present in the Adabas Audit Data Retrieval system for the reader job to be able to process the contents of an ALOG dataset, which is read in as one or more lists.
This section gives an overview of the definitions used by Adabas Audit Data Retrieval for the generation of list indexes.
A matching list definition has to exist in Adabas Audit Data Retrieval (Option 2.1) for each list that is to be read in.
The reader program (B97RDR00) retrieves list names (audit, subscription, userview) from the audit data and maps them to the AAR equivalents (form, extension, report). B97RDR00 finds the best-matching definition for each list via the three-part name (see "Adabas Audit Data Retrieval (AAR) import workflow").
Required settings
Lists must be defined as item lists. Indexing and display are page-based in Adabas Audit Data Retrieval and an item is treated like a logical page. One item contains the data that belongs to one Adabas database transaction, which includes information on client, request, and command data (after image if insert, before image if delete, before and after image if update).
The following panel shows the required settings, which can be found on page 3 of the list definition panel:
PE97LD22 --------------------------------------------------------- Page 3 of 3 Command ===> _________________________________________________________________ Update List/Report Definition Last Update: MALIK1 2020-11-17 13:11:15 Form: FNR100 Extension: QASF100 Report: FILE_100 Read-In and Display Processing Parameters : Copy to Local Spool ===> YES (Y)es,(N)o Document Stack ===> NO_ (Y)es,(N)o Indexing without Definition ===> YES (Y)es,(N)o Item Processing Mode ===> YES (Y)es,(N)o Item Display Mode ===> YES (Y)es,(N)o Layout ===> ________________ (Name or Mask) Press ENTER to update the definition. Press UP to display the previous page. Press END to return to the previous panel. |
Indexing without Definition causes indexes to be created automatically based on the information contained in the metadata of the ALOG datasets.
For detailed information on list definitions, see "List definitions (Option 2.1)".
The reader program (B97RDR00) will retrieve instructions for indexing from the metadata of the ALOG dataset if Indexing without Definition is set to YES in the list definition.
Optionally, you can also create index definitions for each list definition. Indexes are defined locally under an index name for each list (Option 2.1, line command IX). An index definition contains specifications on what to index under which name.
The reader job will apply the instructions contained in the audit dataset and the instructions contained in the index definitions during indexing.
Note on index type: Adabas Audit Data Retrieval supports different types of indexes (see "Index types"). Primary and global indexes can be created according to the instructions contained in the audit dataset and index definitions. The creation of secondary indexes requires index definitions.
Note on instance number: If you need more than one index definition for an index (for example, because the information to be indexed is located at several positions or because identifiers vary), define several instances of the index under the same index name. The values of all instances are stored in the same index. The combination of index name and instance number must be unique.
For detailed information on index definitions, see "Index definitions for lists".
For retrieval, AAV relies on the presence of global indexes. Global indexes are generated in batch by a separate program (B97GLOBL).
Processing instructions for global indexes are defined at the folder level. A list must be assigned to at least one folder if the generation of global indexes is defined for this list.
If index definitions or metadata specify the generation of a global index, the reading in of the list will fail if the list is not assigned to a folder.
Each folder has a layout group assigned to it. The layouts of the layout group define the input fields for the index search.
For more information on folders, see:
For more information on B97GLOBL, see "B97GLOBL: Global index batch utility".
For retrieval, AAV relies on the presence of folder groups. Folder groups, folders, layout groups, and layouts are displayed in the form of an expandable tree structure.
Use a one-to-one relationship between folder group and folder if you don't want to group folders.
For more information on folder groups, see "Folder groups (2.5 GROUPS)".
Layouts are required for global indexes. A layout defines a query mask with input fields for the index search.
Optionally, layouts can be grouped into layout groups. Use a one-to-one relationship between layout group and layout if you don't want to group layouts.
Specify the name of the layout group in the folder or folder group definition.
For more information on layouts and layout groups, see "User-defined query masks (Option 2.6)".