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 Not under consideration
Categories Runtime
Created by Guest
Created on May 23, 2014

Internal Trace should not be allowed to be disabled

Opening this RFC on behalf of the customer in PMR 67263,122,000. They experienced a 2-byte Storage Violation in a TIOA. They run with internal trace turned off, so no history of the storage was visible in the trace table. They were asked to turn all the normal tracing back on and optionally use the CSFE terminal storage checking trap, then wait for a reoccurrence. Hursley Change Team agreed that this was the best approach. This prompted the following response from the customer:

Two weeks on a SEV2 made this issue very visible to Global Senior Management and Staff at xxxxxxxx. A few questions keep coming up:

1.) If all trace options must be ON for IBM to provide proper support, then why is ANYONE allowed to turn them OFF - especially if it means Hursley cannot support their own product?

2.) If it is determined there is a 'cost of turning traces on so IBM can support the product' that impacts our billing, who should be accountable for any increase?

These comments have opened up a dialog with Hursley Development, the Change Team and Level 2 on the value of tracing, and whether a certain level of tracing should be forced on and not allowed to be disabled.

This RFC is being opened to document that discussion and the burden that a recreate request often has on a customer.

Idea priority High
  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Transaction Processing
    Product - CICS Transaction Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server

  • Guest
    Reply
    |
    Jan 16, 2015

    The provision of the ability to turn CICS internal trace on or off has always been provided as an option to enable users to make a decision on incurring the cost of having internal trace active or not. With internal trace inactive one must consider that the possible consequences may be that sufficient diagnostics are not captured to enable problem determination to be undertaken when a problem is encountered, whether that is an application or system related problem. The default setting for CICS internal trace is active but in this case the customer was running with internal trace off so this choice had indeed been made. We have no plans to remove the ability for users to control the internal trace and force it to always be active.