The entries you want are missing from the trace table
Read this section if one or more entries you were expecting were missing entirely from the trace table.
- The trace data you wanted did not appear at the expected time.
- The earliest trace entry in the table was time-stamped after the activity that interested you took place.
- You could not find the exception trace entry you were expecting.
- If tracing for some components or some tasks did not appear, you might not have set up the tracing selectivity correctly. For guidance about checking and correcting the options, see You are not getting the correct task tracing and You are not getting the correct component tracing.
- If you were using GTF tracing, it might not have been active at the time the trace entry should have been made. GTF tracing must be started under MVS™ using the TRACE=USR option.
- If CICS® z/OS® Communications Server exit trace entries (point IDs AP FCxx) were missing, remember that they are only ever made to the GTF trace data set.
- If you attempted to format the auxiliary trace data set selectively
by transaction or terminal, and trace entries for the transaction
or terminal were missing entirely, it could be that you did not capture
the corresponding “transaction attach” (point ID XM 1102) trace entry.
This could occur if the master system trace flag is switched off and
the transaction status is set to special, or if you do not have KC
level 1 tracing selected.
When you select trace entries by specifying TRANID or TERMID parameters in the DFHTU710 trace control statements, DFHTU710 searches for any transaction attach trace entries that contain the specified TRANID or TERMID. It then formats any associated trace entries, identified by the TASKID found in the transaction attach trace entry data.
It follows that you must have KC level-1 tracing selected for the task in question at the time it is attached if you want to format the auxiliary trace data set selectively by transaction or terminal.
For more details about trace formatting using DFHTU710, see Trace utility print program (DFHTU700).
If the options were correct and tracing was running at the right time, but the trace entries you wanted did not appear, it is likely that the task you were interested in did not run or did not invoke the CICS components you expected. Examine the trace carefully in the region in which you expected the task to appear, and attempt to find why it was not invoked. Remember also that the task tracing options might not, after all, have been appropriate.
If the earliest trace entry was later than the event that interested you, and tracing was running at the right time, it is likely that the trace table wrapped round and earlier entries were overwritten.
Internal trace always wraps when it is full. Try using a bigger trace table, or direct the trace entries to the auxiliary trace or GTF trace destinations.
Auxiliary trace switches from one data set to the next when it is full, if the autoswitch status is NEXT or ALL.
If the autoswitch status is NEXT, the two data sets can fill up but earlier data cannot be overwritten. Your missing data might be in the initial data set, or the events you were interested in might have occurred after the data sets were full. In the second case, you can try increasing the size of the auxiliary trace data sets.
If the autoswitch status is ALL, you might have overwritten the data you wanted. The initial data set is reused when the second extent is full. Try increasing the size of the auxiliary trace data sets.
GTF trace always wraps when the data set is full. If this was your trace destination, try increasing the size of the GTF trace data set.
If you cannot find an exception trace entry that you expected, bear in mind that exception tracing is always done to the internal trace table irrespective of the status of any other type of tracing. So, if you missed it in your selected trace destination, try looking in the internal trace table.