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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Allowing one Recoup ECB to process more ordinals in a fixed record type is not intended to reduce Recoup run time. The purpose is to reduce overhead by reducing the number of ECB creates and exits. We understand the purpose of this RFE is to reduce Recoup run time when a very large number of ordinals are in a fixed record type (i.e. 4,000,000,000+ ordinals). If there are 4,000,000,000 ordinals in a fixed record type, the issue is that Recoup will find all 4,000,000,000 records to determine if there are chains. The time required to find the records drives Recoup run time. Reducing the time that Recoup needs to find 4,000,000,000 ordinals depends on several factors including: (1) I/O capacity in the LPAR; (2) I/O capacity in the DASD subsystem; (3) MIPs available on the LPAR; and (4) Available resources on TPF such as available ECBs. There may be other alternatives depending on how many pool records are referenced out of the fixed records.
This RFE does not address the real issue for Recoup run time. A separate conversation is needed to determine the best way to address Recoup run time when there is a large number of ordinals in a fixed record type.