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 219

Cobol JSON PARSE - Keep unparsed JSON Structures/Fields

It should be possible to store everything that is attached under a JSON object that you specify in an Xer field. For example, if I get a list of orders that I then have to pass on to subprograms, I would like to be able to parse {"topic": "xy", "o...
about 2 years ago in COBOL Compilers / z/OS 1 Not under consideration

Option to have spaces treated as zeros at Runtime

Our COBOL V6 migration has been painful and slow. Much of this due to 'invalid data'. The biggest pain for our applications folks are when copy books and linkage areas initialized to spaces at the 01 level. To code around this in V6 is a lot of ex...
almost 4 years ago in COBOL Compilers 4 Not under consideration

Provide ISO 2014COBOL Decimal Floating Point Support

Submitted By: 3100012QSB #56Submitted Date: 2016-06-14, Submitted By: Cheryl Watson
over 8 years ago in COBOL Compilers 4 Not under consideration

Free Source Format

The e-COBOL Compiler should follow the standard 2002 with the definition of free source format. It should be implemented how it was done in COBOL for AIX.- variable length up to 252 columns- existence of area A and area B (not standard-2002!!!)- s...
over 11 years ago in COBOL Compilers 3 Not under consideration

Implement dynamic-capacity tables

Implement dynamic-capacity tables as defined by the COBOL 2014 standard (INCITS/ISO/IEC 1989:2014 [2014]).
over 9 years ago in COBOL Compilers 7 Not under consideration

SSRANGE have more granular suboption such as enabling checking to target (update) fields only

During runtime whenever COBOL code don't well handle for reference modification fields such as below it would cause serious storage overlay especially within CICS. WS-A PIC X(10)WS-B PIC X(20)WS-POS PIC S9(04) COMP MOVE WS-A TO WS-B (WS-POS:) Whil...
over 6 years ago in COBOL Compilers 4 Not under consideration

JSON PARSE error handling messages filter

Cobol Developer coding the JSON parsing and associated Error Handling For JSON PARSE statement, provide a mechanism for the application code to indicate which JSON-STATUS conditions are acceptable and which are to be considered errors.
about 4 years ago in COBOL Compilers 2 Not under consideration

Show inserted CICS elements as part of the source code COBOL listing

When compiling with the COBOL co-processor, when CICS elements DFHEIBLK and DFHCOMMAREA are not coded by the programmer they are inserted by the compiler into the LINKAGE SECTION and as parameters on the PROCEDURE DIVISION statement.The elements d...
about 8 years ago in COBOL Compilers 3 Not under consideration

Enterprise Cobol V6+ - Multi >>WHEN for >>EVALUATE directive

The >>WHEN conditions of the >>EVALUATE directive should behave like the WHEN conditions of the EVALUATE instruction: when several conditions follow one another, without any intermediate text, they should be implicitly linked by an OR.
about 4 years ago in COBOL Compilers 6 Not under consideration

CALLEXIT for checking Call Parameter Usage

It would be good to have a kind of "Call-Exit", which is called every time the compiler see a CALL Subroutine, but also "Procedure Division" or ENTRY-Statement.So we could build a dictionary for all Calls, knowing which program calls which subprog...
about 10 years ago in COBOL Compilers 9 Not under consideration

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.