COBOL Compilers

Showing 218

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

11 VOTE

COBOL function hbound() for tables

COBOL has no easy way to check a table index or subscript against the OCCURS [... TO] {n} TIMES value. You can define an OCCURS constant to check against, but this requires application maintenance correctly preserve the correspondence when the tab...

almost 4 years ago in COBOL Compilers 4 Not under consideration

26 VOTE

Boolean support and bit manipulation

Support for Standard COBOL "Boolean support and bit manipulation".This includes (but is not limited to those I might have overlooked):- Boolean data PICTURE clause, i.e.: USAGE DISPLAY PICTURE 1.- USAGE BIT, i.e.: USAGE BIT PICTURE 1(8).- GROUP-US...

about 9 years ago in COBOL Compilers 6 Not under consideration

5 VOTE

Allow JSON PARSE WITH DETAIL to be set on or off at runtime

JSON PARSE WITH DETAIL ON/OFF It would be helpful if WITH DETAIL can be enabled/disabled at run time by application logic. The WITH DETAIL phrase displays too many messages in job output. Many of the messages are expected conditions for many...

almost 2 years ago in COBOL Compilers / z/OS 2 Not under consideration

9 VOTE

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

As of now, when the API we call return a dynamical JSON array, we need to declare a COBOL array with a large number of occurences in order to be sure to retrieve all the data with the JSON PARSE statements. But, in most cases, the json array will ...

almost 4 years ago in COBOL Compilers 2 Not under consideration

21 VOTE

User defined constants

Implement user defined constants using the COBOL Standard "Constant entry".

about 9 years ago in COBOL Compilers 8 Not under consideration

6 VOTE

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

almost 3 years ago in COBOL Compilers 3 Not under consideration

23 VOTE

Facilitate use of COBOL records in EXEC SQL multi-row operations.

Given a COBOL record like01 X. 05 Y1 ... 05 Y2 ... ...in a COPYbook which could be used as a target for a SQL FETCH(let's say generated by DB2's DCLGEN), we need a mechanism to define an other record like01 table. 03 X . 05 Y1 occurs 100 times ......

almost 11 years ago in COBOL Compilers 9 Not under consideration

8 VOTE

Enterprise Cobol - Compiler option to enable / disable DEBUGGING-MODE

To date, the activation of debugging lines, marked with a "D" in column 7, can only be activated / deactivated by intervening at the source code level, by specifying or removing the "WITH DEBUGGING MODE" clause in the Environment Division. We woul...

almost 4 years ago in COBOL Compilers 13 Not under consideration

2 VOTE

Replace IGYCDOPT - Compiler options - with a regular options file

We want to move away from assembler based product options and modifications to a modern approach with regular parameter files. This approach provides more agility, easier maintenance and easy transparency on used settings. This initiative is not l...

12 months ago in COBOL Compilers / z/OS 1 Not under consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use