You have captured the wrong trace data

There are several ways in which you might capture the wrong trace data. The following points are some sets of symptoms that suggest specific areas for attention

  1. You are not getting the right task tracing, because:
    • Tasks do not trace the right trace points for some components.
    • Transactions are not being traced when they are started from certain terminals.
    • There is no tracing for some terminals that interest you.

    If you are aware of symptoms like these, it is likely that you do not have the right task tracing options set up. Turn to You are not getting the correct task tracing for further guidance.

  2. You are getting the wrong amount of data traced, because:
    • Tracing is not being done for all the components you want, so you are getting too little information.
    • Tracing is being done for too many components, so you are getting more information than you want.
    • You are not getting the right trace points (level-1 or level-2) traced for some of the components.
    • Tasks are not tracing the component trace points you want. This evidence suggests CICS component tracing selectivity is at fault.
    If your observations fit any of these descriptions, turn to You are not getting the correct component tracing for guidance about fixing the problem.
  3. The data you want is missing entirely from the trace table.

    If you have this sort of problem, turn to The entries you want are missing from the trace table for guidance about finding the cause.

It is worth remembering that the more precisely you can define the trace data you need for any sort of problem determination, the more quickly you are likely to get to the cause of the problem.



dfhs12o.html | Timestamp icon Last updated: Monday, 5 June 2017