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
Categories General DB
Created by Guest
Created on Jan 24, 2022

Altering IMS database mapping cases and fields within it using DDL

Based on the current IMS ALTER TABLE syntax documentation, there is currently no way to add a single mapping case or to drop a single mapping case at the moment. You can only drop the complete mapping definition and add it again including the additional mapping case, which should be added, or without the mapping case, which should be deleted. This is hard to do with complex mappings consisting of a large amount of cases. There is currently also no way to add a field to an existing mapping case than to drop the whole mapping and add it again, which is also hard to with complex mappings consisting of a large amount of mappings or even single mappings with lots of fields within it.

To simplify the modification of IMS database mapping definitions, please add an ALTER MAP map_name option to the ALTER TABLE statement with suboptions ADD CASE case_id AS case_name (column_definitions), ALTER CASE case_name (add_alter_or_drop_column_declarations) and DROP CASE case_name. It could potentially be more intuitive to reference a mapping case in a different way when adding, altering or dropping colums, which are part of a mapping case. For instance ALTER TABLE table_name IN DATABASE database_name ALTER COLUMN column_name IN MAP map_name CASE case_name column_alteration_definitions is probably be more intiutive to use than ALTER TABLE table_name IN DATABASE database_name ALTER MAP map_name ALTER CASE case_name ALTER COLUMN column_name column_alteration_definitions. The challenge with the first is, that the keyword IN is already being used with ARRAYs an STRUCTs, which can be also a part of a mapping case. This could be solved by adding the ARRAY or STRUCT name as last part of such an IN clause: ALTER TABLE table_name IN DATABASE database_name ALTER COLUMN column_name IN MAP map_name CASE case_name array_or_struct_name column_alteration_definitions. Another way could be the dot notation you are using with the COMMENT ON statements: ALTER TABLE table_name IN DATABASE database_name ALTER COLUMN map_name.case_name.column_name column_alteration_definitions respectively with ARRAY or STRUCT fields: ALTER TABLE table_name IN DATABASE database_name ALTER COLUMN map_name.case_name.array_or_struct_name.column_name column_alteration_definitions but you should consistently use dot notation and/or IN notation throughout all statements. The dot notation has the problem, that you are concatenating potentially very long names, which makes it hard, where you have for instance a line limitation to 80 characters like when executing the SQL Batch Utility or a potential future native DDL utility.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 21, 2022

    Hi Robert,

    As I had mentioned to you on the phone, we will accept this RFE but we will look at addressing this when we get to the "DDL intuitive" line item in our DDL roadmap. When we get to the "DDL intuitive" line item, we'll look at what all we need to do in making DDL more intuitive / user friendly and then prioritize. Let me know if you have questions.

    Sincerely,
    Deepak Kohli
    deepakk@us.ibm.com