With Adabas Manager, several users can work independently and in parallel with all registered databases on a managed host. Adabas Manager stores frequently used data such as for example database GCB (general control block) information in the main memory of the Windows machine which displays the host (CS layer server).
The caching for each registered user (local objects) and for user-independent (global) objects is kept separate. A local object for example would be information on files that are "under construction", i.e., information from an incomplete file creation process, whereas GCB information of the Adabas databases is viewed as global objects.
After logout or after the session has been ended by closing the browser window, cached objects are no longer available.
To avoid a cache overflow, unused objects are deleted from the cache after a set time limit. A local object is regarded as unused if its user has been inactive for longer than 3600 seconds; a global object is considered unused if its period of inactivity is longer than 7200 seconds.
The cache status can be reviewed and cleared manually.
To display the cache status of an Adabas
Manager session:
Select the Adabas Manager item in the tree-view and right-click on it.
Select on the drop-down menu.
The cache information is displayed in the detail-view.
To clear the cache of an Adabas Manager
session:
Select the Adabas Manager item in the tree-view and right-click on it.
Select on the drop-down menu.
The cache for all users using the same C/S layer server is cleared and all SAF-relevant data is lost. This means that after a cache clear, all users sharing a CS/layer server must logon again.
Internal settings of the cache and timeout limits can be set in the HKLM/SOFTWARE/Software AG/System Management Hub/Products/Adabas Manager/Versions/7.6.3/ registry; the following properties may be modified:
| Sess_Mem_Block | cache size in bytes | minimum: 1000000 |
| Sess_Mem_Max_Global_Idle | maximum lifetime of global objects in seconds | minimum: 3600 |
| Sess_Mem_Max_Local_Idle | maximum lifetime of local objects in seconds | minimum: 3600 |
After modification of a setting in the registry, the cache must be cleared with ; a new cache is set up automatically.
 |
Warning: Please note that serious problems might occur if you modify the registry incorrectly; make sure to exercise great care when working in the registry and only modify the settings listed in this table. |
