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/TPF
Created by Guest
Created on Sep 19, 2017

Report ECB heap control table statistics

The initial ECB heap control table (IEHCT) allows each ECB to reference 151 heap nodes, more than this requires the ECB to get system heap to extend its IEHCT.
As PJ44907 highlights, this process can cause a bottleneck on the system heap lock and depletes system heap by 32,768 bytes per extension.
.
This RFE is to request greater visibility on the IEHCT size so that the user is aware when a specific application is close to this threshold.
.
The fields of interest are:
1) CLHH_EXT_CNT in CCSTOR which is the system wide count of ECBs that extended their IEHCT size.
2) IEHCT_ENTRIES_TOT which is the count of IECHT items from the ECBs own IEHCT header.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 12, 2017

    This information is available with owner name collection (ZMOWN) and resource usage by named limit set collection (ZECBM COLLECT). IBM does not intend to implement this in other functions in the foreseeable future.

    Visibility to fields IEHCT_ENTRIES_TOT and IEHCT_BUF_OBTAINED already exists. These fields are reported in resource usage by owner name collection (ZMOWN) and resource usage by named limit set collection (ZECBM COLLECT). Field IEHCT_ENTRIES_TOT is reported in column titled: "The number of ECB heap control entries that were obtained in the time period." Field IEHCT_BUF_OBTAINED is reported in column titled: "The number of ECB heap buffers that were obtained in the time period." In addition, name value pair collection will report both of these fields.

    Visibility to CLHH_EXT_CNT will be able to be determined. CLHH_EXT_CNT in CCSTOR is used to count the number of ECBs that have their ECB heap hash table resized. When an ECB uses 970 ECB heap control table entries, the hash is resized. Because name value pair collection will report the number of ECB heap control table entries (IEHCT_ENTRIES_TOT), ECBs that need to resize their hash table can be calculated. Any time that IEHCT_ENTRIES_TOT is 970 or higher, the hash table has been resized.