Skip to Main Content
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


Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Aug 10, 2022

Track SHRLEVEL info in Utilities history

In Db2 13 utility execution can be recorded in one or two utilities history tables. We are struggling to find all utility executions ran with SHRLEVEL NONE to tell the applications to change their parameters to avoid problems. It is very hard to find this information today, if even possible. Therefore we suggest that the SHRLEVEL used is recorded in utilities history tables.

Another use-case for the information is to easily find this information if we have concurrency problem, instead of having to look up every single job execution. We could probably even find it by joining the tables to for example Omegamon tables with deadlock and timeout information.

Needed By Quarter
  • Guest
    Reply
    |
    Nov 8, 2022

    I agree strongly with this idea. Our shop standard is for all utilities to be run as SHRLEVEL CHANGE whenever possible. But trying to identify utilities, such as REORG, which have been run with SHRLEVEL NONE or SHRLEVEL REFERENCE, does not seem to be possible by looking at SYSIBM.SYSCOPY. Registering the SHRLEVEL for all utilities, even if it's for informational purposes, would be extremely helpful.