ADABAS Caching - Separate Priorities for Cached Components

Hello

I wish to recommend a change to ADABAS Caching which allows different caching priorities for the ASSO and Data components of a file. Typically I find that it would be very useful to have the ability to vary the ASSO priority from the file's associated DATA priority to avoid memory wastage. Metrics for caching are currently 1.)overall ASSO cache available and the file's requirements from this cache >as well< as 2.)overall DATA cache available and file's DATA requirements from the available DATA cache and so you can see that there is an unnecessary constraint when attempting to select a size for both file components rather than one component. I feel that independence of priority of ASSO and Data would avoid a great deal of compromise in cache settings (do I accept lesser performance or do I waste memory?) and while many sites now would have large memory allocations for their production environments (compared to the memory sizes available when ADABAS Caching was first released) neither lesser performance nor waste of memory are acceptable.

Example might be :

ADARUN CFILE=(053,5,ASSO,VIRTUAL64)

ADARUN CFILE=(053,4,DATA,VIRTUAL64)

Currently these parameters would result in both ASSO and DATA having a caching priority of 4. My suggestion is that it would be better to allow separate caching priorities per >file component< (ASSO/DATA) rather than per >file<.

Thank you for listening.

Brent Harrison