Support in-core records for performance

TPFUG_Req_Number: DF00079
Contact Originator Id: PSP/KLM
Abstract: Index records should have the option of being core resident fixed file records for performance reasons. Some data structures are so heavily used that designers think it is not wise to use TPFDF. Although a HIT rate in VFA may go up to 100%, the record has to be moved to working storage every time. It is suggested that a mechanism is implemented which 'locks' loose ordinals/blocks in working storage, refreshes them after an update, hooks them to a DBDEF slot. The records must be heavily used, seldomly Updated, completely transparent to the application. TPFDF should support in-core records whether they reside above or below the 16 M line, and the TPFDF calls for in-core records should have a short path length to optimize performance. TPFDF should provide the ability to split residency of records (by ordinal ranges etc) in the DBDEF.
Description: Index records should have the option of being core resident fixed file records for performance reasons. Some data structures are so heavily used that designers think it is not wise to use TPFDF. Although a HIT rate in VFA may go up to 100%, the record has to be moved to working storage every time. It is suggested that a mechanism is implemented which 'locks' loose ordinals/blocks in working storage, refreshes them after an update, hooks them to a DBDEF slot. The records must be heavily used, seldomly Updated, completely transparent to the application. TPFDF should support in-core records whether they reside above or below the 16 M line, and the TPFDF calls for in-core records should have a short path length to optimize performance. TPFDF should provide the ability to split residency of records (by ordinal ranges etc) in the DBDEF.