Serviceability Aids › Enhanced System Tracing › Saving Trace Data

Saving Trace Data

Saving system trace data increases the information available for problem diagnosis. When saving trace data, CA IDMS periodically writes trace entries to a persistent data store: either a trace area or a log area.

A trace area is a new type of system area that can be defined in Version 18.0. It is similar to a log area and, to be usable, it must either be included in the SYSTEM segment or be accessible through the SYSTEM DBNAME. It differs from a log area in that its name is DDLDCTRC instead of DDLDCLOG. The new trace area is archived and printed using the new ARCHIVE TRACE and PRINT TRACE utility statements. Just as for a log area, a job to archive the trace area can be automatically submitted using the WTO exit.

When you enable saving trace data, consider the following:

• If a trace area is defined in the run time DMCL, trace entries are written to the trace area rather than the log area. Trace information is never written to a sequential log file.
• If large volumes of trace data are to be saved, you should define a trace area to minimize the impact on system throughput.
• If an adjunct table exists, only its contents are saved.
• If a system trace table exists without an adjunct table, the contents of the system trace table are saved. This can generate high volumes of trace output.