Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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 IBM i
Categories Db2 for i
Created by Guest
Created on Mar 2, 2022

Add Support for COMMENT ON to SQL VIEW, SEQUENCE etc.

Add support to add OBJECT TEXT (COMMENT ON or LABEL ON in SQL terminology) to those SQL-created objects that are currently not supported. by the COMMON ON statement.
Such as VIEWS, SEQUENCES, TRIGGERS etc.


Use Case:

Today, when you create (for example) an SQL VIEW, the COMMENT ON SQL statement cannot be used to apply object-level text. To do that, you need to insert the CL: CHGOBJD CL command to the object.
However, if that object has a LONG NAME, that name may not be the same each time the routine being run is performed, so you have to do it later. With the COMMENT ON support, we can specify the long SQL name and have it apply the text to the object as expected.


Idea priority Medium
  • Guest
    Reply
    |
    Mar 4, 2022

    Since the requested support has existed for many years, this RFE is being declined.

  • Guest
    Reply
    |
    Mar 4, 2022

    Okay, using COMMENT ON and failing, I tried LABEL ON.
    Again, specifying TABLE instead of VIEW worked for me.
    SEQUENCE(s) also seem to work using LABEL.

    Thank you MTosney and IBM Dev.
    We can close this one.

  • Guest
    Reply
    |
    Mar 4, 2022

    Um... the online documentation and the system say otherwise, or I'm "missing a comma" somewhere.
    I've tried COMMENT ON and LABEL ON for a VIEW and cannot get anything other than:
    Message: [SQL0104] Token DATAF1 was not valid. Valid tokens: (.
    I then went into the legacy STRSQL and typed in COMMENT ON and press F4 and see this list which does not include view:
    1=File
    2=Field
    3=Package
    4=Index
    5=Procedure
    6=Parameter
    7=Alias

    So in light fo the comments in this RFE, I decided to try COMMENT ON TABLE instead of VIEW.
    That worked! It changed the VIEW's object text.
    Interesting.

    I still cannot do that for Sequences, however unless there's a trick to that as well????
    Thanks.

  • Guest
    Reply
    |
    Mar 3, 2022

    IBM needs to understand the function gap you are seeing.

    The LABEL statement generates system object text for objects, including views, sequences, and triggers. The COMMENT statement generates long descriptions that are stored in the database catalog tables. Is there something about the LABEL support that is not adequate for your use case?

  • Guest
    Reply
    |
    Mar 2, 2022

    I think you can already do this. COMMENT and LABEL both support sequences and triggers explicitly.

    For views in particular, you need to use the COMMENT ON TABLE/LABEL ON TABLE syntax with the view name.