This provides a trace of activity over a time period within the main CAS facilities.
When active, this feature flushes trace records to disk before the trace table is overwritten.
Note: Be sure that you have adequate disk space available before activating auxiliary trace because the output file can become very
big very quickly. If you have a high-activity system, you can limit the size of the output file by also configuring the maximum
size of the diagnostics file. Writing out to a file also degrades performance.
Because it runs while the system is running, it can affect the performance of the system, and is therefore very configurable
in order to record the specific types of events that might be needed for different types of problems. Ideally, production
systems should be able to perform adequately with at least the minimum tracing enabled.
Trace file datasets
For auxiliary traces, you have the option in
Enterprise Server, to write trace output to either an A or a B dataset file. The default is A, but you can toggle between the two.
Output files
Trace output files are written to your system directory, and take the following form:
- casauxta.rec
- Output file for the A dataset.
- casauxtb.rec
- Output file for the B dataset.
Note: To view a video on the Micro Focus YouTube channel, on how to enable AUX tracing for Enterprise Server using the Legacy Enterprise
Server Administration User Interface,
click here. While the UI is different than ESCWA, the concepts are the same.