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

Clear

Ideas

    Showing 357 of 9161

    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 7 years ago in COBOL Compilers 4 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 9 years ago in COBOL Compilers 3 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 11 years ago in COBOL Compilers 9 Not under consideration

    Add the ability to obtain ODO counter with the JSON PARSE statement

    It would be really useful to us to be able to parse dynamic JSON arrays into ODO COBOL tables, with the JSON PARSE statement giving us the number of actual occurrences filled. Ideally by automatically update the ODO counter. It would also be very ...
    almost 3 years ago in COBOL Compilers / z/OS 2 Not under consideration

    Update DFSFDLS0 to disable OPTCD=W for virtual tape subsystems

    Please make the changes for IMS to allow me to disable OPTCD=W for tape logging with a parameter in //DFSVSAMP a permanent feature of IMS. This was originally released to the IMS population as a usermod created by Dave Viguers. It needs to be buil...
    over 9 years ago in IMS System Services / General System 1 Not under consideration

    TYPE56FA TLS Transaction Level Statistics Log Record does not show the actual Input Queue Time for PtP switches

    The actual Transaction Input Queue Time can not be taken from TYPE56FA Log Records for PtP Messages processing.Field TPINUTC, that Customer wants to subtract from field TPSTARTU to get the Input Queue Time, is in fact the Timestamp when the first ...
    over 8 years ago in IMS System Services / General System 3 Not under consideration

    IGY-Compiler-Messages are not summarized at the end of the SYSPRINT

    In cobol-versions pre 5.1. all IGY-compliler-messages (info, warning, error, severe) are summarized at the end of the SYSPRINT-output . In Cobol 5.1.1 and above these messages are displayed anywhere and not always in one block.
    over 9 years ago in COBOL Compilers 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 5 years ago in COBOL Compilers 4 Not under consideration

    Help identifying moves causing invalid numeric values

    Different move statements can cause invalid numeric values to be stored in numbers.This will cause dumps when compiling with NUMPROC(PFD) and ZONEDATA(PFD). We would like the compiler to help the programmers identify these statements at compile ti...
    almost 6 years ago in COBOL Compilers 1 Future consideration

    To enable an option in the COBOL compiler to get the DB2 integrated coprocessor behaves as the separated DB2 precompiler does

    We have been using the COBOL 4.2 compiler for years in our shop. We have just begun to use the integrated SQL coprocessor, instead of the separated DB2 precompiler and we are experiencing problems with the continuation lines. The manual says the p...
    about 11 years ago in COBOL Compilers 48 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.