COBOL Compilers

Showing 274

Allow specification of xsi:schemaLocation on NAMESPACE for XML Generate.

In order to correctly validate a generated xml we are required to specify the xsi:schemaLocation for the used namespace. The current implementation of XML Generate allows to specify a namespace, but it does not allow for specification of a schemaL...

almost 4 years ago in COBOL Compilers 5 Future consideration

3 VOTE

XML Generate not aware of CDATA section, was: case numer TS004007239

Handling of Data within a CDATA Section when generating XML is incorrect. The COBOL compiler starts to escape characters within a CDATA section when that section contains (valid) XML. According to the official XML standards, it should NOT modify A...

almost 4 years ago in COBOL Compilers 9 Not under consideration

4 VOTE

Cobol - New Reserved Words to reduce hard coding

My suggestion is Cobol should have two new reserved words containing the currently executing Section / Paragraph name i.e. CURRENT-SECTION / CURRENT-PARAGRAPH (both would have an implicit picture clause X(30). Typically this would be useful in err...

over 5 years ago in COBOL Compilers 9 Not under consideration

4 VOTE

Ability to track older version of compiled cobol code

My customer is interested in tracking other versions of Cobol below 5.2. They have a utility to run against there cobol loadlibs that produces the different levels and counts but they have no way of determining when and how often they are used. Th...

over 5 years ago in COBOL Compilers 12 Not under consideration

7 VOTE

SSRANGE with Suboptions

SSRANGE can test tables with one dimension. It's not able to test each row and column of a multi-dim-table. It would be nice to have an option with can test multi-dimensional tables.For example:SSRANGE(STD) is the same like SSRANGE in presenceSSRA...

over 9 years ago in COBOL Compilers 3 Not under consideration

3 VOTE

Compile warning when using COMP-5 larger than 9 digits

When using COMP-5 variables many developers are not aware of the performance impact of using COMP-5 with variables defined longer then 9(9).Therefore we would like a warning added to the rules(nolaxperf) option, that will indicate this, and recomm...

about 4 years ago in COBOL Compilers 1 Future consideration

2 VOTE

COBOL Compile option 'NUMCHECK(MSG)' function improvement request

We applied the COBOL Compile option 'NUMCHECK(ZON,MSG)' to prevent 'invalid data' that may occur during program execution.As a result of testing, we found that there were a lot of programs with 'invalid data' code.Program developers have the follo...

almost 3 years ago in COBOL Compilers 2 Not under consideration

2 VOTE

Entreprise COBOL V6+ - IGYOS4081-U when MDECK(NOCOMPILE) + SQL options and no valid DBRMLIB

When compiling with MDECK(NOCOMPILE) and SQL options to resolve COPY and EXEC SQL INCLUDE, the compiler raises an IGYOS4081-U error if the DBRMLIB ddname is not declared, or if file associated with the DBRMLIB ddname does'nt have a valid format. T...

almost 3 years ago in COBOL Compilers 1 Not under consideration

5 VOTE

COBOL-JAVA interoperability via JNI: use DirectByteBuffers and avoid copiyng data between COBOL workarea and Java byte array

The biggest hit we expect from DBB is that memory does not need to be copied between COBOL workarea and Java byte array Detail are described in the attached file

about 7 years ago in COBOL Compilers 8 Not under consideration

5 VOTE

Reference Modification Abend if Lenght is a Not a Positive Integer

If the calculation of the length in a reference modification is zero or negative, there could be unpredictable/unexpected results. Due to our un-comfort with these unpredictable results, we'd like to see an abend, at runtime, when the length is ze...

about 7 years ago in COBOL Compilers 5 Not under consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use