Reloading archived data automatically

When you retrieve and display information from an indexed list and the list or its indexes are no longer online, Adabas Audit Data Retrieval automatically reloads the required data from the archive.

The query panel displays for each field whether the corresponding index is online or not.

Which data is automatically reloaded?

When you are searching a list whose indexes are offline, all indexes required for the query are reloaded from the archive.

When you are browsing pages or hit pages, Adabas Audit Data Retrieval will not reload the entire list. Instead, it will reload only a 4-MB block of data containing the page to be displayed.

Reloading archived data manually

Automatic reloading may lead to repeated mounts of the same archive volume, namely:

• When a list has several indexes and users specify several searches each involving different indexes
• When users are displaying several pages of a list and these pages are located in different 4-MB blocks of data

Under these circumstances, it may be more effective to reload the entire list manually in order to reduce the number of mounts.

A manual reload for the list is carried out by entering the line command R in front of the list. This command creates a reload request (see "Displaying and deleting reload requests"). The list is actually reloaded at the next run of the reload batch utility. For more information, see "B97RLD: Reload batch utility" and the Adabas Audit Data Retrieval User Guide.

Where is the data reloaded to?

When data is reloaded automatically, indexes are reloaded to the Adabas Audit Data Retrieval index spool and 4-MB blocks of data are reloaded to the Adabas Audit Data Retrieval cache spool.

When data is reloaded manually, indexes are reloaded to the Adabas Audit Data Retrieval index spool and lists are reloaded to the Adabas Audit Data Retrieval online spool.

Automatic reload from archive when searching

When you want to search a list:

1. Adabas Audit Data Retrieval checks whether all indexes to be searched are present in the index spool.

   If yes, Adabas Audit Data Retrieval carries out the search.

2. If one or several indexes are not in the index spool, Adabas Audit Data Retrieval reloads the index(es) from the archive and carries out the search.

Automatic reload from archive when browsing

When you want to display a page of a list:

1. Adabas Audit Data Retrieval checks whether this page is present in the online spool.

   If yes, the page will be displayed.

2. If the page is not in the online spool, Adabas Audit Data Retrieval checks whether the page is in the cache spool.

   If yes, the page will be displayed.

3. If the page is not in the cache spool, Adabas Audit Data Retrieval will reload the 4-MB block of data containing the page from the archive to the cache spool and then display the page.

Automatic reload when using background search

When you start a query and at least one of the required indexes is offline, Adabas Audit Data Retrieval offers the following options:

• You can start the search immediately.

  The disadvantage of this method is that the screen remains locked until the number of hits is displayed.

• You can trigger the reloading of all required data without starting the search immediately.

  The advantage of this method is that you can continue to use your screen after submitting the query while Adabas Audit Data Retrieval reloads the required indexes to the index spool and the 4-MB block containing the first hit page to the cache spool. To display the hits of the search, just repeat the search at a later point in time.

Which archive dataset is used for reloading?

If a list as been archived more than once, the availability of the archive datasets (retention period and status Good/Bad) and the reload order specified in the definitions determines which archive dataset is used for reloading.

If the Order for Reload field in the archive pool definition specifies ASIS (as is), lists and indexes are reloaded from the archive dataset whose archive subpool has the lowest value in its Order for Reload field. If this archive dataset is no longer available or if accessing this dataset leads to an error, the data is reloaded from the archive dataset(s) of the archive subpool with the next higher reload order.

If the Order for Reload field in the archive pool definition specifies a numeric value, lists and indexes are reloaded from the archive dataset whose archive subpool has this value in its Order for Reload field.