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 Future consideration
Created by Guest
Created on Jul 24, 2019

Internally Indexed RDS Tables within SAzOS

The Systems Automation(SAzOS) tool would greatly benefit from being able to support Table data that is Internally Indexed. Currently the CREATE sub-function within INGRDS does not support creating tables that are internally indexed. There needs to be the ability to create tables and then manipulate and query the data within these tables with Primary and even Secondary keys.

Benefits of having Internally Indexed Tables are as follows, but not limited to:
• Ease support for complex and dynamic data structures.
• Eliminate duplicate and/or similar data entries.
• Greatly improve the efficiency and performance of table queries. This benefit is elevated even further when the queries are against tables that are frequently accessed and/or contain a large number of rows and/or columns.
• Improve the manageability and maintainability of any data structures, especially large ones.
• Allow the Joining or Linking table data.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 3, 2019

    Raimund,
    Thanks for letting me know the status of this RFE! I do appreciate that you are at least retaining this concept for future reference! I do believe if SAzOS utilizes an internal DB for the PDB that is truly indexed, that this functionality should be easily made available to its users also. So I assume that is what you are referring to for the "SA 4.2 Data Store".

    Also just as a note … I believe that this 134861 RFE was created because 116092 with the same Title of "Internally Indexed RDS Tables within SAzOS" was inadvertently closed. However, the difference is 134861 only has one vote, whereas 116092 had 6 votes.

    Thank you!

    Gordon Larsen

  • Guest
    Reply
    |
    Oct 11, 2019

    Raimund,
    Thanks for pointing out the KEY parameter! I am pretty sure this was IBM's first attempt at resolving indexed tables. If it is, this was developed for us at our request. We tested it out when it was first made available. However, it fell short in testing to meet the requirements that only an internally indexed table can meet. Since that was at least a couple of years ago I no longer remember what the KEY parameter external indexing fell short on, but it was several things. I think some of the things were being able to join tables and eliminating duplicates or similar data entries. There were other shortcomings with the KEY parameter functionality.

    When I was at AOTC this Spring it was mentioned by the developers that IBM was going to implement internal tables that would meet these requirements. I assume this is still being developed?

    Thank you!

    Gordon Larsen