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 Subscribe
Status Not under consideration
Workspace COBOL Compilers
Created by Guest
Created on Nov 7, 2018

RELATED IDEAS

Entreprise Cobol - Internal format for INDEX with offset and occurrence number

The internal storage format of an INDEX uses four bytes to store the offset relative to the beginning of the memory table (as long as the compiler generates 31-bit addressing code).
We propose to use a storage format consisting of these four bytes containing the offset and another four bytes (or more) containing the occurrence number in the memory table in binary format.
This should optimize performance when comparing INDEX to numeric values representing the occurrence number in a table in memory. The extra cost involved in SET operations on INDEX must be largely offset by the gains obtained when searching for the value of the occurrence number corresponding to the offset contained in INDEX.

This would also make it possible to compare an INDEX DATA-ITEM with a numerical value, by exploiting the "occurrence" part of the INDEX internal storage format, as well as to compare an INDEX DATA-ITEM with another INDEX DATA-ITEM or an INDEX NAME, based on the "occurrence" part rather than the "offset" part.

Idea priority Low
  • Guest
    Reply
    |     Apr 24, 2020

    No reply from submitter. Cancelling RFE.

    Feel free to open a new RFE if you are able to answer the latest questions. Thanks.

  • Guest
    Reply
    |     Feb 9, 2020

    Hi,

    Any updates regarding our previous question?

    If we don't receive a reply by March 10th, 2020, we'll assume this RFE is no longer required.

    Thanks.

  • Guest
    Reply
    |     Apr 11, 2019

    Hi, can you please confirm if there is an existing performance problem (or possibly another issue) that you are trying to resolve with this RFE? If so, can you please explain this in detail?

  • Guest
    Reply
    |     Jan 2, 2019

    Hi, is there an existing performance problem (or possibly another issue) that you are trying to resolve with this RFE? If so, can you please explain this in detail?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.