IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Not under consideration
Workspace z/TPF Product Family
Categories z/TPFDF
Created by Guest
Created on Feb 11, 2014

RELATED IDEAS

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.

Idea priority Low
  • Guest
    Reply
    |     Oct 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/TPF

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - z/TPF

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.