IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Feb 4, 2019

RELATED IDEAS

Allow RUNSTATS SHRLEVEL CHANGE to operate as the name says

This RFE is a result of the PMRs (31614,112,848) we have opened where the root cause was identified as invalid values in RTS tables. Current design allows to re-initialize certain fields in RTS (eg. TOTALROWS) only by executing RUNSTATS SHRLEVEL REFERENCE. This is of course an obstacle as every serious shop cannot afford running utilities using SHRLEVEL REFERENCE for obvious reasons. The same functionality should be provided when running RUNSTATS SHRLEVEL CHANGE. As other utilities, SHRLEVEL CHANGE allows utulity to "see" all the changes that happened to the data stored in the object being referenced and the same should be the case for RUNSTATS. Current design does not give option to re-initialize broken RTS in some cases as utilities to run to fix it need correct values in RTS which are broken (if try to use REORG), or access to object must be restricted which is not acceptable for business. The problem manifest itself very well when there is a lot of objects affected and you cannot determine which is wrong and to what extend.

  • Guest
    Reply
    |     May 10, 2019

    Hello,

    I am not sure how to and whom to contact to respond to this decision so I put the comment here.

    I am not sure how you ended up in discussing and giving it a comprehensive review and you missed the fact that I am not raising idea to update TOTALROWS, but to make RUNSTATS a utility which will finally catch up with the direction where DB2 is going with all utilities and functionality. Which is, that all utilities executing with SHRLEVEL CHANGE, at the completion of utility they know about all the changes which happened at the time the utility was running, not ignore the those changes. As far as I know, REORG also (based on parameters) operates by scan when it unloads the rows. If reorg can understand changes that happened when it run - why runstats cannot? Maybe you should actually give a comprehensive review to the actual idea here, not TOTALROWS column update?

  • Admin
    Janet Figone
    Reply
    |     May 9, 2019

    Thank you for submitting this Db2 for z/OS enhancement request.

    After giving the request a comprehensive review, we have determined that we cannot include it as a candidate in an upcoming product deliverable because it is not consistent with the product direction.

    Due to the nature of RUNSTATS SHRLEVEL CHANGE we cannot have it update RTS TOTALROWS. The reason is that it operates by scan, and it's conceivable that inserts occur behind the scan process and would not be seen. Therefore this solution is likely to make RTS less reliable rather than more.

    As a consequence we will not be implementing this request.

    We appreciate your input to the Db2 for z/OS development team.  We also hope that you will continue to submit ideas for improvements as customer feedback is a key component  to shaping the future direction of Db2 for z/OS. 

    Sincerely,

    Db2 for z/OS Team

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.