z/OS

Showing 51

Allow OMITTED parameters in function identifier.

The COBOL 2002 standard allows for the OMITTED keyword to be specified as a parameter to a function identifier. This should be allowed for Enterprise COBOL. It could be implemented in a manner similar to specifying OMITTED as a parameter in a CALL...

7 months ago in COBOL Compilers / z/OS 4 Future consideration

5 VOTE

JSON PARSE WITH DETAIL specified at run time

It would be helpful if WITH DETAIL phrase of JSON PARSE can be enabled/disabled at run time by application logic. We continue to struggle with problem resolution when specific use cases cause unexpected results from web service calls, resulting in...

11 months ago in COBOL Compilers / z/OS 3 Not under consideration

3 VOTE

Provide COBOL support for YAML and utility to convert DTD to a COBOL record definition,

We have a data structure/format in .YAML /YML file. And require ability/utility to convert YML DTD to a COBOL equivalent copybook

7 months ago in COBOL Compilers / z/OS 2 Not under consideration

4 VOTE

JSON PARSE error details

JSON PARSE error handling improvements - Expose Parse messages to application code. We continue to struggle with problem resolution when specific use cases cause unexpected results from web service calls, resulting in Parse failures. Displaying th...

11 months ago in COBOL Compilers / z/OS 1 Future consideration

7 VOTE

Handle abend when using JSON GENERATE statement

We are facing an issue when using the JSON GENERATE cobol statement with cobol variables containing incorrect value. For exemple, in the case of a numeric variable containing spaces, the order triggers an ASRA abend and the generated json buffer i...

almost 2 years ago in COBOL Compilers / z/OS 2 Planned for future release

8 VOTE

Introducing Local Working Storage (Valid only inside a Section)

Hi, it would be great, if COBOL would allow local variables which would be defined into a COBOL section and are valid only in this COBOL Section. This would bring a huge benefit making COBOL programs much more structured and reducing the working s...

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

2 VOTE

IBM Enterprise COBOL - Add support for BINARY-CHAR, BINARY-SHORT, BINARY-LONG, BINARY-DOUBLE as alternative to COMP-5

Hi, The COMP-5 USAGE, (or TRUNC(BIN) compilation option), allows binary values to be stored according to the entire storage capacity of the machine's internal representation. However COMP-5 is a constructor implementation and have portability...

7 months ago in COBOL Compilers / z/OS 3 Future consideration

1 VOTE

Make name of DLL generated for COBOL-Java ILC variable

Fixed prefix LIB might not fit to naming conventions

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

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

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

6 VOTE

JSON PARSE error handling improvements

JSON PARSE error handling improvements - Expose messages and tokens to application code. It would be helpful if application logic can determine which PARSE messages to display or suppress. Also, message tokens can be useful in error handling in...

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

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use