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.
See this idea on ideas.ibm.com
Dear Madam/Sir
We upgraded from Enterprise COBOL v4.2 to v6.3 in 2022. Since then we have enabled various checks provided by the new compiler like PARMCHECK, INITCHECK and NUMCHECK. During these three years we are trying to correct our programs that have uninitialized variables. These programs generate IGYCB7311 during the compilation. However, we face difficulties on this as a lot of programs have been written more than 20 years ago and we cannot easily change them. In addition we experience high cpu consumption using INITIALIZE statement especially in big tables.
We have been informed by IBM that in the new versions of COBOL (V5/V6), the underlying storage typically contains garbage. In previous COBOL versions the storage that was obtained from TGT happened to be zeroed.
So Instead of using CPU heavy INITIALIZE statements or leave a lot of programs without properly INITIALIZed variables, we want the storage that is provided by the system to uninitialized variables to be zeros, in a similar way to previous COBOL versions.
Kind regards
Konstantinos Zafeiropoulos
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
This idea is being discussed internally and requires more time.