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 280 of 8524

COBOL Z/OS support LRECL greater than 32767

Hi, Like for ZFS files i want that COBOL can support records greater than 32767. In USS environment i can create, read a record greater than 32767, in Z/OS VBS record format i can't.The LRECL=X is supported on JCL.
almost 12 years ago in COBOL Compilers 6 Not under consideration

Make available additional source code information, used at compilation, in load module

We'd request that the location of the source code that was used during program compilation be made discoverable or available within the load module. For our purposes this would extend to COBOL, C/C++, PL/I, Assembler, Java. Our product team is req...
about 4 years ago in COBOL Compilers 3 Not under consideration

Enterprise Cobol V6+ - comment directive

We suggest implementing a "comment" compilation directive. This could be the >>* directive. This directive would allow comments to be introduced in a source code, which would not be returned to the compilation listing (so as not to overload ...
about 4 years ago in COBOL Compilers 6 Not under consideration

DB2 SQL TYPE ROWSET FOR n ROWS

To facilitate the declaration of host-variables necessary for multirow access in DB2, I suggest the creation of a new SQL type dedicated to the creation (generation) of structures with OCCURS on elementary variables. SQL TYPE IS ROWSET FOR n ROWS ...
about 6 years ago in COBOL Compilers 2 Not under consideration

Provide ISO 2014 COBOL Literal Enhancements

Copied from old SHARE Requirements system SSLANG13001; Voting Priority=2.8 +5=2 +4=5 +3=4 +2=11 +1=2 abstain=3 Priority=2.8 NOTE 1: This is a follow-up (possible replacement for): SSLNGC08006 2002 ISO COBOL - Enhanced literal continuation support ...
over 8 years ago in COBOL Compilers 5 Not under consideration

Compiler Directives

We do not like the inclusion of the compiler directives and the commenting out of non-included statements.We think all directives and non-included statements should be excluded from the source listing.
about 4 years ago in COBOL Compilers 5 Future consideration

Enterprise Cobol V6 - Invalid binary code for set address by reference modification on a unbounded dataitem and SSRANGE

Hi A SET ADDRESS OF / TO ADDRESS OF statement from a unbounded dataitem, and in the presence of the SSRANCE option, generates an invalid binary code: message IGZ0072S / IGZ0308W is triggered unconditionally. The same code compiled in NOSSRANGE run...
about 4 years ago in COBOL Compilers 3 Is a defect

Cobol V6R2 - Improvement of the binary code generated for EVALUATE statement

The binary code generated for an EVALUATE statement has some defects:- dead code- test and branch not optimumProblems found with all optimization levels. The binary code generated in Cobol V4R2 option OPTIMIZE (STD) is better than the binary code ...
over 6 years ago in COBOL Compilers 6 Is a defect

Question: support of ALTERNATE DDNAME LIST for COBOL programs

Hi, Is the use of ALTERNATE DDNAME LIST possible with programs created by the IBM Enterprise COBOL compiler? If yes, how to know the order of the ddnames at the level of the compiled program? If not, register a change request to allow it. Reas...
about 2 years ago in COBOL Compilers / z/OS 7 Not under consideration

Support SYSOUT for dynamic file allocation

Enterprise Cobol support dynamic allocation for file (use of an environment variable named with ddname an file parameters in value for allocation).But if we try to allocate a SYSOUT, this raise an error IGZ0251W at run time... It would be desirabl...
about 9 years ago in COBOL Compilers 7 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.