Tracing has gone to the wrong destination
In terms of destinations, CICS® system trace entries belong to one of three groups - internal tracing, auxiliary tracing and GTF tracing.
- CICS trace entries, other
than CICS z/OS® Communications Server (SNA) exit traces
and exception traces, go to any of the following trace destinations
that are currently active:
- The internal trace table
- The current auxiliary trace data set
- The GTF trace data set.
- CICS Communications Server exit traces that are not exception traces go only to the GTF trace data set, if GTF tracing is active.
- CICS Communications Server exit traces that are exception traces go to the internal trace table and, if GTF tracing is active, to the GTF trace data set.
- All other CICS exception traces go to the internal trace table and to any other trace destination that is currently active.
For CICS system tracing other than exception traces and CICS Communications Server exit traces, you can inquire on the current destinations and set them to what you want using the CETR transaction.
CETR - trace control illustrates what you might see on a CETR screen, and indicates how you can change the options by overtyping the fields. From that illustration you can see that, from the options in effect, a normal trace call results in a trace entry being written to the GTF trace destination. If an exceptional condition occurred, the corresponding exception trace entry would be made both to the GTF data set and to the internal trace table, even though the internal trace status is STOPPED.
Note that the master system trace flag value only determines whether standard tracing is to be done for a task (see Table 1). It has no effect on any other tracing status.
- Internal tracing
- goes to the internal trace table in main storage. The internal trace table is used as a buffer in which the trace entries are built no matter what the destination. It, therefore, always contains the most recent trace entries, even if its status is STOPPED—if at least one of the other trace destinations is currently STARTED.
- Auxiliary tracing
- goes to one of two data sets, if the auxiliary tracing status is STARTED. The current data set can be selected from the CETR screen by overtyping the appropriate field with A or B, as required. What happens when the data set becomes full is determined by the auxiliary switch status. Make sure that the switch status is correct for your system, or you might lose the trace entries you want, either because the data set is full or because they are overwritten.
- GTF tracing
- goes to the GTF trace data set. GTF tracing must be started under MVS™, using the TRACE=USR option, before the trace entry can be written. Note that if GTF tracing has not been started in this way, the GTF tracing status can be shown as STARTED on the CETR screen and yet no trace entries are made, and no error condition reported.