Rational RFE Community

Welcome users! Here you have an opportunity to collaborate directly with the product development teams and other product users.

Note: The RFE Community now supports Security Systems as a brand. As part of this security branding, several products that were formerly Rational products are now reclassified as Security Systems products. Along with this product realignment, RFEs that were associated with these products have been migrated to be assigned to their new Security Systems product families. If you do not see your request under Rational, please search for it under Security Systems.

Filter the page content by brand and product


Search   

This is a table showing requests
Number of votes Request headline and description

17
votes

TRIM Intrinstic function

Implement COBOL 2014 Standard TRIM intrinsic function.

Uncommitted Candidate

16
votes

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

Uncommitted Candidate

15
votes

Perform until exit

Now that COBOL finally has proper EXIT statements there should be a way to speciify an "infinite" loop, or rather a loop that has no explicit end condition but depends on the use of EXIT PERFORM (or E...

Declined

15
votes

User defined constants

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

Uncommitted Candidate

14
votes

Flag uninitialized but used Variables

The compiler should flag Fields, which are used, but not initialized

Uncommitted Candidate

9
votes

COBOL5: extended DIAGTRUNC feature for detecting variables size mismatch

COBOL 5 behaves differently than in previous versions, in some scanarios, as in the following case:  

- Programs that move data to and from data items that at run time contain values not conforming t...

Uncommitted Candidate

9
votes

Implement dynamic-capacity tables

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

Declined

7
votes

Improve COBOL 5 IPCS dump formatting

Using IPCS under COBOL 4.2 and earlier, it was relatively easy to locate a program's Working Storage.    Under COBOL 5, this is a multi-step manual process.

This request is to improve COBOL 5's IPCS du...

Uncommitted Candidate

3
votes

Cobol V5 - STGOPT does'nt optimize SQL--* variables created par SQL option

Cobol V5 compiler, as Cobol V4 compiler, can process DB2 SQL commands through the integrated coprocessor (instead of a pre- compilation) .

When the SQL compiler option is enabled, the "automatic" var...

Submitted

3
votes

DB2 and CICS pre- compilers do not recognize Cobol V5 floating comments

COBOL V5 allows use of "floating comment", sequence space + " * >" followed by a free text.

DB2 pre- compiler (tested with DB2 V10) and CICS pre-compiler (tested with CICS TS 4.2) do not recognize th...

Submitted

3
votes

Cobol 5    Sort Table in-place

Sort in Enterprise COBOL 5.2 does not sort in-place when sorting an array in storage, but instead allocates a work copy of the array to perform the sorting and allocates additional storage as well.
Th...

Uncommitted Candidate

3
votes

ECOBOL v5.1 - CEE0813S Insufficient storage.

I created Service Request 89561,7TD,000 to resolve a CEE0813S Insufficient storage issue a user was having.

As per the SR, a 'quick fix' should make the August release but may not resolve the issue.
...

Uncommitted Candidate

2
votes

Cob5: Enhancements Compile Listing Option MAP

PP 5655-W32 IBM Enterprise COBOL for z/OS    5.2.0

With compile option MAP the total size of working-storage or WSA is not included in compile listing. 

Enterprise Cobol 4.2 and its predecessors are s...

Submitted

2
votes

Cobol V5 - Error displaying ARCH option in CEEDUMP - ARCH(10) shown as ARCH...

CEEDUMP displays the compile options of a program compiled with Cobol V5.

ARCH information seems incorrect : it is returned to 0 as we compile with ARCH (10).

Submitted

2
votes

Cobol V5 - constant expression 2 ** 31 not resolved by optimizer at compile...

The compiler does not resolved the expression "2 ** 31" in a comparison statment or in a compute statment, and generated code do a call to IGZXPR2 runtime routine (this is expensive at runtime).

Uncommitted Candidate


View all

Your ideas matter!

As of today:

9 new
3 planned
18 delivered


45 users
513 votes
303 comments

Give us feedback

Participate in the RFE Community survey to help us improve your experience.