COBOL Compilers

Showing 277

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.

almost 4 years ago in COBOL Compilers 6 Not under consideration

10 VOTE

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

almost 8 years ago in COBOL Compilers 3 Not under consideration

12 VOTE

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

almost 10 years ago in COBOL Compilers 9 Not under consideration

4 VOTE

Enterprise Cobol - Reconciliation between Listing line number and Source line number

We are in the process of deploying the implementation of a DevOps approach on the mainframe. In particular, we want to implement code coverage and unit test follow-ups (automated tests). Market tools, especially the SonarQube tool, work with the S...

over 3 years ago in COBOL Compilers 2 Not under consideration

10 VOTE

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 8 years ago in COBOL Compilers 1 Not under consideration

8 VOTE

COBOL 6 should use zIIP processor

The Enterprise COBOL Compiler Version 6 (and also V5) use much more CPU Resources than Version 4.Not only 12 Percent, but Factor 12.We need 12 times more CPU for compiling than in the older versions.Some parts of this workload should be zIIP-enabl...

almost 7 years ago in COBOL Compilers 2 Not under consideration

3 VOTE

SSRANGE Functionality Enhancement

Enhance SSRANGE regardless of selected option (MSG/ABD) to stop memory overlays when starting position for reference modification exceeds target data field length.

over 2 years ago in COBOL Compilers 1 Not under consideration

6 VOTE

Enterprise Cobol V6 - Suppress conflict between the DYNAM and CICS options

The conflict between the DYNAM and CICS options could be resolved by implicitly introducing a compilation directive ">>CALLINTERFACE STATIC" before "EXEC CICS" and a compilation directive ">>CALLINTERFACE" after the "END-EXEC" clause. ...

over 5 years ago in COBOL Compilers 2 Future consideration

11 VOTE

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

almost 10 years ago in COBOL Compilers 48 Not under consideration

9 VOTE

Implement dynamic-capacity tables

Implement dynamic-capacity tables as defined by the COBOL 2014 standard (INCITS/ISO/IEC 1989:2014 [2014]).

about 8 years ago in COBOL Compilers 7 Not under consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use