Skip to Main Content
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.

Status Not under consideration
Categories z/TPFDF
Created by Guest
Created on Feb 11, 2014

DF12196 TPFDF ? Allow Parallel IO with LRECS (non-LLR)

TPFUG_Req_Number: DF12196
ORIGIN DATE: 10/23/2012
REQUIREMENT ABSTRACT (required)

TPFDF Parallel IO – TPFDF should provide an option so that normal subfiles can be retrieved using IOs done in parallel rather than sequential.


REQUIREMENT DESCRIPTION (required)

Provide an option within DBDEF so that the file is stored in a format conducive for parallel IO. The file can then be retrieved by doing say up to 16 FINDCs followed by a single WAITC within TPFDF. The application would still continue to read one record at a time as is done today. A copy of the LREC to heap, as is done in case of LLRs BAM, is not needed in this case since the LRECs are small and should be optional.


CRITICAL SUCCESS FACTORS (optional)



ALTERNATIVE SOLUTIONS (optional)

LLRs could be used to implement a solution at the application level. Application will have to do its own management of the smaller lrecs within the LLR. Searching using keys, order of lrecs will again need to be handled by the application. This would be very in-efficient.
SOLUTION CONSIDERATIONS (required)

TPFDF needs to store file pointers multiple file pointers in the 4k block, instead of just the forward chain. This may be stored as TLRECs. Re-coup will also need to be modified to handle this scenario.

Idea priority Low
  • Guest
    Reply
    |
    Mar 21, 2018

    This RFE's Headline was changed after submission to reflect the headline of an internal request we were already considering, but will now track here.

  • 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