COBOL Compilers

Showing 280

Lifting File Structure Limitations

For I/O usability enhancement i suggest to allow lazy file definitions.In COBOL it is always a problem to read files which differs in file description between program code and file system.Example: FD INFILE RECORDING F.01 INRECORD PIC X(80).When t...

almost 11 years ago in COBOL Compilers 4 Not under consideration

1 VOTE

Enterprise COBOL - Introduce equivalent of conditional compilation in management of compilation options in SYSOPTF

Hi, Managing compilation options can be complex due to the multiplicity of contexts: batch, cics, db2, static call, dynamic call, etc. This complexity is increased when several versions of the IBM Enterprise COBOL compiler must coexist with opt...

about 1 year ago in COBOL Compilers / z/OS 1 Not under consideration

6 VOTE

New COBOL Compile Option: Global ON SIZE ERROR

When you want to handle overflow conditions and want to avoid truncated fields you have to code the ON SIZE ERROR statement for all computational statements.This is tedious work.In addition any decimal overflows conditions were suppressed by Langu...

over 6 years ago in COBOL Compilers 5 Not under consideration

4 VOTE

Enhance INITCHECK(STRICT) for different types of used-before-set warnings

Given:INITCHECK(LAX) will issue IGYCB7311-W when a data item is completely uninitialized on all logic paths leading to that statement. INITCHECK(STRICT) will issue IGYCB7311-W when a data item is uninitialized on any logic paths leading to that st...

over 4 years ago in COBOL Compilers 2 Not under consideration

7 VOTE

SSRANGE suboption to check for a modified length resulting in a negative length

A new SSRANGE suboption is needed that should be useable also in production.This suboption should create extra checking code only if a "modified reference" (that modifies the default length of a variable) involves a variable value. In this case th...

almost 8 years ago in COBOL Compilers 4 Not under consideration

4 VOTE

Message added with the sysout

Our request is at the NUMCHECK compilation option ... MSG versus ABD sub-option. When we put NUMCHECK (ZON (ALPHNUM), PAC, NOBIN, MSG), In runtime when the INVALID DATA is encountered, a nice message is added in the SYSOUT like for example: IGZ027...

over 4 years ago in COBOL Compilers 5 Not under consideration

10 VOTE

COBOL-Program with no goback or Exit Programs

Writing a COBOL program without any GOBACK, EXIT PROGRAM or STOP RUN will produce a runtime error. It's necessary to get a warning by the compiler if none of these "BR14" are written

over 11 years ago in COBOL Compilers 6 Not under consideration

5 VOTE

Separate NUMCHECK's MSG/ABD suboptions by type

We're trying to ease our developers into NUMCHECK, and have mostly got PAC through, using the parameter NUMCHECK(NOZON,PAC,NOBIN,ABD) unless specifically requested to downgrade to NUMCHECK(NOZON,PAC,NOBIN,MSG) for a temporary duration (until the c...

almost 6 years ago in COBOL Compilers 2 Not under consideration

2 VOTE

Dynamically called programs as smf data

The cobol 6.4 runtime can deliver a report about the dynamically called programs. It would be nice if this information could also be exported as smf data, so that is would be more easy to run analysis about the usage of programs. Currently in smf ...

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

3 VOTE

Enterprise Cobol - INEXIT / PRTEXIT examples and facilities

The INEXIT and PRTEXIT exits make it possible to intervene on the source code read before processing by the compiler, and on the Listing produced by the compiler before restitution. The Cobol Report Writer component uses these exits: it transforms...

over 3 years ago in COBOL Compilers 3 Future consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use