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

COBOL Compilers

Showing 272 of 8228

Enterprise COBOL V6+ - IGYLI0245-E error falsely triggered ("varname" was not defined as a compilation variable)

A conditional compilation variable is used under control of a >>if varname is defined directive.The compiler wrongly triggers an error IGYLI0245-E on the fact that the variable is not defined. The triggered message is an error...The return c...
over 2 years ago in COBOL Compilers 6 Is a defect

Enterprise Cobol - Free from the constraint of the organization of Divisions

Hi, According to the standard, a COBOL program must be organized into 4 Divisions, and these Divisions must appear in a specific order.It is the same with the standard Sections of the Divisions, such as for example the Working-Storage Section or t...
over 2 years ago in COBOL Compilers 10 Not under consideration

Compiler support for +80 character lines

With the release of the IBM Z Open Editor for Visual Studio Code, more IBM COBOL is edited in an editor not limited by 80 characters.We request an option to the z/OS COBOL compiler, to be able to read COBOL code without a limit of 80 characters.An...
over 2 years ago in COBOL Compilers 3 Not under consideration

Let Enterprise Cobol Compiler exploit zIIP CPU

Starting from version 5, enterprise cobol compilers have increased the cpu used to compile programs, especially using optimization options of the executables.Offload the CPU used by compilers to zIIP processors at least during the most cpu busy ph...
over 2 years ago in COBOL Compilers 2 Not under consideration

JSON numeric/string conversion

Support conversion between COBOL numeric fields and JSON strings.
over 2 years ago in COBOL Compilers 10 Future consideration

Enterprise Cobol V6 - Still problems after PH35652 / PH36690 and trace program compiled with OFFSET

After applying fixes PH35652 (COBOL 6.3) and PH36690 (COBOL 6.2), we notice that there are still problems to trace the execution of programs compiled with the option OFFSET / OPTIMIZE (1|2). Despite the use of the OPTIMIZE (1) option, it happens t...
over 2 years ago in COBOL Compilers 6 Not under consideration

COBOL Compile option 'NUMCHECK(MSG)' function improvement request

We applied the COBOL Compile option 'NUMCHECK(ZON,MSG)' to prevent 'invalid data' that may occur during program execution.As a result of testing, we found that there were a lot of programs with 'invalid data' code.Program developers have the follo...
over 2 years ago in COBOL Compilers 2 Not under consideration

Entreprise COBOL V6+ - IGYOS4081-U when MDECK(NOCOMPILE) + SQL options and no valid DBRMLIB

When compiling with MDECK(NOCOMPILE) and SQL options to resolve COPY and EXEC SQL INCLUDE, the compiler raises an IGYOS4081-U error if the DBRMLIB ddname is not declared, or if file associated with the DBRMLIB ddname does'nt have a valid format. T...
over 2 years ago in COBOL Compilers 1 Not under consideration

Enterprise COBOL V6+ - Provide a way to identify source lines discarded by conditional compilation

We have made extensive use of conditional compilation to provide a COBOL development framework. If the development framework is easy to use, the result is a compilation listing filled with lines of source code commented out by conditional compilat...
over 2 years ago in COBOL Compilers 4 Future consideration

XML PARSE BUG XML-TEXT parsing in chunks rather than a single string

XML PARSE BUG XML-TEXT parsing in chunks rather than a single stringXML-TEXT content is 104069, but its separating the text like 64909 and 39160 chars chunks rather than a single string text. we tried Enterprise COBOL 4.2 & 6.2 no difference s...
almost 3 years ago in COBOL Compilers 3 Not under consideration