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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
There are two existing techniques for getting round this problem.
The older method was make use of the distinction between RSECT, for which the RENT check always applies, and CSECT, which is only checked when RENT option is specified. The initial value could then be coded as a CSECT and references to the labels in that CSECT would allow write access without giving a reentrant check error.
A newer and more complete solution is that if the relevant USING statement is a dependent USING, HLASM now chains down to the base USING before checking the section type. This means that a writable copy of a read-only area can be defined as follows:
USING REC_COPY,R2
REC USING MODEL_REC,REC_COPY
...
REC_COPY DSECT
This solution is self-documenting, in that it makes it clear that the base area is a copy, and it is easy to use.
We would agree that the documentation relating to reentrant checks could be improved to provide more detail about how the check works and how to use this technique to avoid spurious warnings. We hope to do this some time soon. However, we do not see any significant need at present or in the near future for any further changes to the implementation in this area.