Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

ADD A NEW IDEA

Clear

Ideas

Showing 396 of 9153

Need Intrinsic Function equal to STCKCONV macro

Provide an Intrinsic Function that performs the same conversion as the STCKCONV Assembler macro to eliminate the necessity of writing and maintaining a separate Assembler subroutine to perform the STCKCONV action.
over 5 years ago in COBOL Compilers 3 Future consideration

Enterprise COBOL - Native handling of output streams equivalent to stderr and stdout

HI, COBOL programs compiled with IBM Enterprise COBOL for z/OS only support a single output stream associated with the DISPLAY statement. A priori, running under MVS, this output stream corresponds to STDERR (file descriptor number 2) in other l...
5 months ago in COBOL Compilers / z/OS 2 Future consideration

CTG COBOL Batch interface like BAQCSTUB - CTGCSTUB.

Rather than using Batch COBOL EXCI to single CICS region, have a COBOL Call interface like zCEE BAQCSTUB. This would allow for CPSM Workload distribution, across target Batch Processing regions. Topology of (Batch Owning Region),.. BOR --> AOR ...
11 months ago in CICS Transaction Gateway / Runtime 0 Future consideration

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...
over 1 year ago in COBOL Compilers / z/OS 4 Future consideration

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...
about 5 years ago in COBOL Compilers 4 Not under consideration

Enhancing CTG Idletimeout paramater definition for Transactions or Group of Transactions

The Idletimeout parameter with dropworking specifies the period of time, in milliseconds, that a connection is allowed to remain idle. When the idle timeout has expired, the Client application is disconnected. Currently Idletimeout parameter can o...
almost 3 years ago in CICS Transaction Gateway / Runtime 0 Planned for future release

User defined constants

Implement user defined constants using the COBOL Standard "Constant entry".
over 10 years ago in COBOL Compilers 8 Not under consideration

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...
almost 3 years ago in COBOL Compilers / z/OS 2 Not under consideration

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 ...
about 5 years ago in COBOL Compilers 2 Not under consideration

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...
about 6 years ago in COBOL Compilers 3 Future consideration