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.
This RFE is one of a small group which had apparently been set aside incorrectly years ago and subsequently overlooked. We are sorry for the delay.
The development team previously investigated various possibilities for optional operand type checking, including length checks, as a possible feature of the TYPECHECK option introduced for HLASM 1.5 in 2004. However, when similar checks were applied experimentally to existing source code, they either caused a surprisingly large number of false warnings (including in code generated by system macro instructions) or they failed to detect genuine errors, so these checks were not implemented at the time. There are also now many z/Architecture instructions where mask or length operands determine the type and length of other operands, making assembly-time checking very tricky.
We understand the requirement, and are keeping it on file, and it may be possible in future to identify and implement a level of length checking which would provide a useful benefit for a reasonable amount of effort. However, this currently has a low priority compared with other work so we are unlikely to implement this in the near future, so at present we cannot accept this request.