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.
The SHEAPC (and tpf_sheapc) API is used to allocate recoverable system heap. SHEAPC ACTION=GET will obtain a system heap buffer. If the request was for a recoverable system heap buffer, the GET will obtain a buffer in either the recoverable system heap area or the 64-bit system heap area. It will not be split between the two areas.
SHEAPC ACTION=EXTEND will obtain another system heap buffer that is associated with the unique token (ISHPXUT) that is required for the SHEAPC call. In order to use the EXTEND option, a GET using the same unique token must have been done first. It is possible that the system heap buffer that was obtained by the GET and by the EXTEND are in different areas. For example, the GET might have obtained a system heap buffer in the recoverable system heap area and the EXTEND might have obtained the buffer in the 64-bit area. This is the scenario that is being discussed in this idea.
ZDSHP FIND buffer_address only locates the first system heap buffer that is associated with the unique token. Therefore, you can only see the system heap area for the first buffer.
ZDSHP unique_token shows all associated buffers with the unique token. This includes the system heap area where they reside.
The ZDSHP unique_token option provides what has been requested by this idea.