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.
There are a few options here that currently exist. The user can use MSG instead of ABEND, at least while debugging ( as the user can't put in DISPLAY statements without recompiling anyway).
Or the user can simply not use NUMCHECK.
Is there a specific reason as to why the user *wouldn't* want to know about invalid data as early as possible? There are three cases in which the DISPLAY would abend. Either:
- The invalid data is used after the DISPLAY statement, and abending on the DISPLAY statement is a good thing, as that means the user identifies the invalid data as early as possible, so it's easier to trace it back to its source.
- The invalid data isn't used after the DISPLAY statement (at least, not in the current program; it could be passed to another program without triggering a numcheck if a parent group is passed); the DISPLAY becomes the only way, in that program, to identify the bad data.
- The item containing invalid data is overwritten without being used after the DISPLAY statement. In this case, the user can still use NUMCHECK(MSG) instead, or make the change to correct the data before the DISPLAY statement instead.
Due to the above reasons, this RFE is currently being rejected.
"Customer would like the "check" only on ARITHMETIC OPERATION not on other instruction" change to
"Customer would like the "check" only on ARITHMETIC OPERATIONs and conditions, not DISPLAY statements"