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
Hi,
As explained in requests COBOLVUE-I-319
and COBOLVUE-I-352
, we want to be able to exclude certain comment lines both from the compilation Listing but also in the expanded source produced by the MDECK
compilation option.
The *CONTROL NOSOURCE
option allows you to exclude lines in the resulting Listing, (not only comments), but is not taken into account by the MDECK
compilation option: the lines are included in the expanded source.
We could use conditional compilation by using a dedicated variable and testing it with a >>if
/ >>endif
to exclude lines, at the source code level before compilation, therefore applicable to the expanded source created by the MDECK
compilation option , and consequently also at the level of the compilation Listing, but this seems dangerous to us because in this case we are not only excluding comment lines.
I renew and reformulate my request COBOLVUE-I-319
to have an option to exclude comment lines, and only comment lines, both in the expanded source created by the MDECK
compilation option, but also in the Listing compilation.
For this I propose to combine a new conditional compilation directive, which would be >>*
, with the CONDCOMP
compilation option:
CONDCOMP(NOSKIPSRC)
: the comment line directive >>*
is included in the expanded source and in the listing
CONDCOMP(SKIPSRC)
: comment line directive >>*
is excluded from the expanded source and the Listing
Use case: online documentation of a Development Framework (explanatory comments in the Framework copybooks) which is not useful in a compilation Listing nor in the expanded source and which only unnecessarily overloads them.
Thanks.
Idea priority | Medium |
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.
Hi Denis,
Thank you for opening this idea. We have evaluated it and have come to the conclusion that having the compiler remove comments is not inline with our current plans primarily because other tools can potentially perform this task and we do not believe many clients will benefit from this item.
Since this idea does not fall within our current strategy, we will be rejecting it. Thank you.
and Listing (filtered).
See attached files with a sample of a "base" COBOL program and resulting "expanded" source with Framework copybooks.
Consider all comments between *CONTROL NOSOURCE / *CONTROL SOURCE wich are documentation of Framework, useless in program.