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.

Status Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Apr 14, 2017

Create STATIC STORAGE section for Cobol

Fixed, static, final, constant... data are embeded in the load module and move to WORKING at program initialization. For large tables in an transactional application server like CICS, it is done millions of time eating a lot of CPU.

a NEW storage section for this r/o constants may be read from the code itself (rent) saving CPU and sharing the low levels caches.

Idea priority Medium
  • Guest
    Reply
    |
    Jul 26, 2017

    The gains of doing this is not worth the risk. Hence, this RFE is being rejected.

    Also, there are risks if TEST is used; or if groups are passed as parameters. A section for r/o constants already exists and it is labelled as the CONSTANT area in the listing.

  • Guest
    Reply
    |
    Jul 11, 2017

    There are two new features of the latest COBOL standards that might be preferred over this request for a non-standard enhancement. These are "constant entries" and "constant records". Some examples:

    01 my-large-literal CONSTANT 'a very large literal goes here'.
    01 my-large-static-record CONSTANT RECORD.
    05 field-1 VALUE 'value of field 1'.
    05 field-2 VALUE 'value of field 2'.
    01 my-large-static-reclen CONSTANT GLOBAL LENGTH OF my-large-static-record.

  • Guest
    Reply
    |
    May 17, 2017

    The RFE is under consideration.

  • Guest
    Reply
    |
    Apr 22, 2017

    Tables with Constants in Working-Storage Section are quite common in our Cobol applications and we also observe the overhead (both cpu and heap storage) when these areas are built at each enclave initialization in CICS.
    This also applies to other needed constants like the more than 1000 MQ option constants from MQ copy books.
    Being able to declare constant data in a cobol program should provide plenty of opportunity to the compiler to generate more efficient code. Putting the constants into the reentrant code csect would also protect the constants from being overridden in a CICS environment with RENTPROT.