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 Delivered
Categories EGL Language
Created by Guest
Created on Dec 14, 2009

Fast access to global constants in COBOL

The only way we know to define global constants in EGL is by defining public, i.e. non-private, consts in a library. We are concerned that this does not perform well in COBOL since constants defined in EGL libraries are translated to a COBOL external method invocation.
Access to global variables should be cheap, both in COBOL and Java.
We are satisfied with libraries as a container for constants and would be reluctant to change from libraries to another vehicle. It should take no longer to access a global constant in an EGL library than it does a global constant in a native COBOL program.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Business Developer

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Business Developer

  • Guest
    Reply
    |
    Mar 24, 2010

    The following solution is implemented in 7.1.0.4 and 7.5.1.4:

    If a library variable is defined with CONST, then a flag (and logic) is added to the variable in the programs that access it (the non-library ones). The accessing of the variable on the 1st time will still cause the external method invocation, but from that point on (2nd through N accesses in that same program), the flag will indicate that the value has already been obtained, and will simply cause the code to reuse the previously-obtained value.

    We still need to call the library on the 1st occurrence, because we need to get its value.

    This implementation gives good performance when a constant is used repeatedly, but still preserves the ability to change the constant value in the library without requiring regeneration of every program that uses the constant.

    If this implementation is not enough to meet your requirements, please open another RFE.