COBOL Compilers

Showing 280

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

over 9 years ago in COBOL Compilers 6 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

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

2 VOTE

Create a new compiler option, SSCHECK, to validate the value of subscripts used in table references

The compiler is able to catch the situation where a subscript for a table reference is hard-coded as zero. For example: 000037 DISPLAY "W-VALEUR-O2(0 J) = <" W-VALEUR-O2(0 J) '>'results in this compiler error:37 IGYPS2017-E "0" was found as ...

9 months ago in COBOL Compilers / z/OS 2 Future consideration

8 VOTE

Enterprise COBOL V6+ - Provide a way to identify source lines discarded by conditional compilation

We have made extensive use of conditional compilation to provide a COBOL development framework. If the development framework is easy to use, the result is a compilation listing filled with lines of source code commented out by conditional compilat...

about 3 years ago in COBOL Compilers 5 Future consideration

4 VOTE

Enabling suppression of null valued decimal numbers in JSON generate

We have a use case where we sometimes need to return a decimal value of 0.00 in a JSON, and sometimes need to return without that value(suppressed). We do not believe that we currently are able to do that. We move low-values to a decimal variable,...

over 1 year ago in COBOL Compilers / z/OS 2 Future consideration

12 VOTE

COBOL: free "ID" for datadefinitions (REST-Services)

In REST-service-context „id“ is a common used keyword for indentification purposes. In COBOL it isn't possible to define such a variable, because it is an reserved word. ID is an abbreviation for IDENTIFICATION in IDENTIFICATION DIVISION and for t...

almost 5 years ago in COBOL Compilers 3 Future 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".

over 9 years ago in COBOL Compilers 8 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

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use