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 is currently available in COBOL V6.3. We ship a sample MSGEXIT with the product that has the sample code to change INITCHECK messages to SEVERE:
From the sample IGYMSGXT in the COBOL product SAMPLIB:
*****************************************************************
* Change severity of message 7311(W) to 12 ('S') *
* This is the case of INITCHECK messages about *
* uninitialized data items *
*****************************************************************
When(7311)
Compute EXIT-USER-SEV = 12
More info can be found here:
https://www.ibm.com/docs/en/cobol-zos/6.3?topic=option-processing-msgexit
Hi,
I'm not sure this is a good idea ...
The "inventiveness" of developers is limitless (in a bad sense), and the compiler should not be a sticking point for developers.
The proof of a correct code is its execution, not its compilation.
For information, with the switch from COBOL V4 to COBOL V6 we took the opportunity to set up a compilation with a maximum of debug option for the test phases, followed by a recompilation with performance or tolerance options for the production.
For example on invalid numeric data, initially we triggered abends: no more programs were running!
We had to go down to a warning level!
The developers do not understand ... because "in COBOL V4 the program worked" and they question the behavior of COBOL V6 declared "not compatible" ... and in fact, despite the numerical errors, programs provide the right results! (with tolerance compilation options: zone with binary zero, with space, even in certain cases alphabetical but with the half byte on the right compatible ...).
So ok to provide compilation alerts, but no blocking.
You always have the option of setting up an msgexit to change the severity level of compiler diagnostics.
The compiler message exit can be used to increase the severity of a selected message or messages.
https://www.ibm.com/docs/en/cobol-zos/6.3?topic=option-processing-msgexit