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 Aug 17, 2012

Improve handling of "Aux Trace Full" condition

Currently, this situation occurs all too frequently:
the support centre asks a customer to create a CICS AUX
Trace; the customer does so, but the trace data set
becomes full and is closed.
The customer then sends in a truncated trace.
The support centre asks the customer to enlarge the
trace data set and re-run the problem re-creation.

Can CICS be changed so that it reports to the user that
the trace data set became full and was closed before
his testing was complete.

So when the user enters CEMT SET AUX STOP he
gets an error message indicating that the file closed
prematurely because it was full.

Idea priority Medium
  • 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
    |
    Aug 28, 2012

    The ability in CICS TS 4.2 and higher to allocate a very large internal trace table removes the need for aux tracing and hence avoid the problem entirely.

  • Guest
    Reply
    |
    Aug 26, 2012

    Hi Tony,
    I know you are not talking about the internal trace but aux trace. My point is don't use Aux trace. Use a very large internal trace table above the bar, run the test, take a dump. Job done. No aux wrap problem and no internal trace wrap problem if you make it big enough.

  • Guest
    Reply
    |
    Aug 20, 2012

    This problem can be avoided entirely with CICS TS 4.2 and higher by allocating a very large internal trace table above the bar, running the test and taking an SDUMP, thus avoiding the AUX TRACE wrap problem. Please advise if this is an acceptable workaround.

  • Guest
    Reply
    |
    Aug 20, 2012

    Sorry... I'm not talking about the internal trace table, which wraps.
    I'm talking about the DFHAUXT Auxiliary trace data set.
    This data set can become full (and can also switch to DFHBUXT.)
    CICS writes a message to the MVS and CICS logs - but these may not
    be seen by the user who started and stopped the trace.