Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

ADD A NEW IDEA

My ideas: COBOL Compilers

Showing 280 of 8524

message IGYRC5122-U is confusing

IGYRC5122-U A RECURSIVE ENTRY TO THE COBOL ABORT MODULE OCCURRED is issued when a compilation abends due to Exscessive CPU time but does not give a clear explanation.?
almost 8 years ago in COBOL Compilers 1 Not under consideration

Enterprise Cobol - Way to not display the IGZ0201W message at runtime

For a file in Variable format with read acces, the COBOL runtime performs a check on the LRECL. By default, if the LRECL does not match the program statement this triggers an abend and an IGZ0035S message. If we declare a FILE-STATUS on the file, ...
almost 4 years ago in COBOL Compilers 4 Not under consideration

Enterprise Cobol - Align the behavior of the EXIT instruction with the ISO standard

In the ISO COBOL standard, the EXIT statement should only be used as a single statement in the single sentence of a paragraph or section.It allows a paragraph or section to be declared without a meaningful statement, usually for the purpose of bei...
almost 4 years ago in COBOL Compilers 3 Not under consideration

ISRLEMX should expand Copybooks even if COPY is not the first word of the line

I try expanding copybooks into our sources using ISRLEMX. But this doesn't work for most of our Cobol-programs as ISRLEMX only seems to work if COPY is the first word of the line. ISRLEMX should support all possible COPY codings supported by the C...
about 4 years ago in COBOL Compilers 6 Not under consideration

Enterprise Cobol - Source text replacement in string

The REPLACE and COPY REPLACING directives allow replacements to be made in the source text, but these replacements only apply to COBOL words. Unless we are mistaken, it is not possible to carry out replacements in string type literals. We suggest ...
about 4 years ago in COBOL Compilers 4 Not under consideration

Enterprise Cobol V6+ - String operators for >>DEFINE directive

The >>DEFINE directive should allow manipulation of strings:* concatenation of strings: use of the "&" operator* substring extraction: use of reference modifications* reference to a compilation variable, possibly with automatic casting
about 4 years ago in COBOL Compilers 2 Not under consideration

Enterprise Cobol V6+ - >>PUNCH directive to include text in source

We would like to have a directive allowing to introduce calculated lines of text (not predefined in a COPYBOOK) in the source code at compile time. We suggest the provision of a >> PUNCH directive. Syntax: >>PUNCH [AT column] text-expr...
about 4 years ago in COBOL Compilers 1 Not under consideration

Enterprise Cobol V6+ - >>PERFORM VARYING for loop

We propose the implementation of a compilation directive allowing to do iterations. These iterations could involve the manipulation of compilation variables and source text which would then be replicated on each iteration of the loop.Corrollary: y...
about 4 years ago in COBOL Compilers 2 Not under consideration

Enterprise Cobol V6+ - Dynamic compilation variable

Compiler directives, and in particular the >>DEFINE directive, are not handled by the REPLACE and COPY REPLACING directives. This therefore prohibits managing compilation variables dynamically, for example by declaring in a COPYBOOK a compil...
about 4 years ago in COBOL Compilers 1 Not under consideration

Enterprise Cobol - empty SECTION and statement in SECTION without PARAGRAPH

We see unexpected behavior of the Cobol compiler when using SECTION in PROCEDURE DIVISION.This for the V4R2 and V6R2 versions. Case 1 When a SECTION is empty, SECTION declaration followed immediately by another SECTION declaration, the compiler is...
about 4 years ago in COBOL Compilers 5 Not under consideration