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 comment from the RFE community is appropriate. Users should not code this. We have recently added code to the compile to flag its usage under RULES(NOGOTO). But accurately detecting the lack of an IGNORE CONDITION is difficult and not the best use of our limited development time. Users should heed the RULES(NOGOTO) message and clean up the code
We may fulfill this RFE by flagging any use of EXEC CICS HANDLE and suggest that it be replaced by a test of EIBRESP
The customer should *NOT* be using EXEC CICS HANDLE, but code their request with the NOHANDLE option and follow that with a SELECT(EIBRESP)/WHEN/WHEN/WHEN/OTHER statement to provide a structured handling of the unexpected condition!!!
EXEC CICS HANDLE (and that other abomination, EXEC SQL WHENEVER) are in essence GOTO statements, and as any programmer worth his or her salt should know, GOTO statements were already deemed harmful in more than 60 years ago, in 1968 in Edsger Dijkstra's letter "Go To Statement Considered Harmful", see http://www.cs.utexas.edu/users/EWD/ewd02xx/EWD215.PDF