IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories BCP_Service Aids
Created by Guest
Created on Mar 6, 2023

RELATED IDEAS

Enhance granularity for CTRACE_DEFAULT_OR_MIN Health Check

Currently, the CTRACE_DEFAULT_OR_MIN Health Check is an "all or nothing" proposition--that is, there is no way to tell the Check that it is "OK" to be using non-default or "minimum" trace parameters for any one specific Component.  So, if any one Component is using non-standard trace values *and* that is as expected because the System Programmers and/or IBM have determined that they want to run a specific Component with non-default trace parameters (such as for long-tern First Failure Data Capture), then after the default of 7 days, the Check will start reporting an exception.  There is no way to tell the Check to "ignore" the non-default trace parameters for a specific Component and only report an exception when any *other* Component trace is active with non-default trace parameters.  It would be helpful if each site could identify those Component(s) that are using non-default parameters to prevent the Check from reporting an exception unless some other/new CTRACE Component were active with non-default values.  As it is today, this Check will *always* report an exception, thus making this a "boy who cried wolf" situation for this Check and the only way to avoid it is to effectively deactivate the Check.

Idea priority Low
  • Guest
    Reply
    |     Mar 29, 2023
    This item is unlikely to be given high enough priority to be included in a release plan.

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.