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.
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
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Transaction Processing
Product - z/TPF
Component - z/TPF
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - z/TPF
Component - Runtime
This may be a misunderstanding of how Record ID 0 is used and how data collection counts it.
You should never have a record ID of zero in a BCA. If an undefined record ID is in VFA, which is an exceptional case (described below), it will contain the actual record ID. Since undefined records assume the default VFA-NO attribute, ZVFAC USAGE skips them.
Record ID zero is tolerated in the FARW of a FIND request (where the actual record ID may be unknown to the application). The FIND request uses the default RIAT attribute of VFA-NO. If the record is not already in VFA, it will not be brought in. If the record happens to be in VFA from a previous I/O using the correct record ID, the BCA will contain the actual record ID - not zero. Since FILE does not allow a record ID of zero, you can't put a record ID of zero into a BCA. Therefore, allowing ZVFAC USAGE to search for zero record IDs in VFA will yield no results. FINDs using record ID zero that are satisfied from a VFA buffer are counted by Data Collection since the record may actually be a VFA candidate.
If a record ID is undefined in the RIAT, it also assumes the default attribute of VFA-NO. The only time an undefined record ID will reside in VFA is when a VFA buffer is used for a FILE operation because the working storage block is not releasable. In that case, the buffer remains on the reserve list after the write operation completes, but since it has the VFA-NO attribute it will be flushed as soon as it is found by a subsequent FIND or when reallocated for another file address. I/Os to undefined records are not counted by VFA Data Collection because of the VFA-NO attribute. The VFA buffer is only used as a temporary output block in this case.