Use the exception option to redirect exception trace data to <filename>.
If the file does not already exist, it is created automatically. If it
does already exist, it is overwritten. Optionally, you can limit the file
to nnn MB, at which point it wraps nondestructively to the beginning. If you
do not limit the file, it grows indefinitely, until limited by disk space.
Optionally, if you want the final trace filename to contain today's date,
the PID number that produced the trace, or the time, do one of the following
steps as appropriate (see also the examples at the end of this section).
- To include today's date (in "yyyymmdd" format) in the trace filename,
specify "%d" as part of the <filename>.
- To include the pidnumber of the process that is generating the tracefile,
specify "%p"" as part of the <filename>.
- To include the time (in 24-hour hhmmss format) in the trace filename,
specify "%t" as part of the <filename>.
Examples
- Trace output goes to /u/traces/exception.trc. No
size limit:
-Xtrace:exception.output=/u/traces/exception.trc,maximal
- Output goes to except and wraps at 2 MB:
-Xtrace:exception.output={except,2m},maximal
- Output filename contains today's date in yyyymmdd format (for example, traceout.20041025.trc):
-Xtrace:exception.output=traceout.%d.trc,maximal
- Output file contains the number of the process (the PID number) that
generated it (for example, tracefrompid2112.trc):
-Xtrace:exception.output=tracefrompid%p.trc,maximal
- Output filename contains the time in hhmmss format (for example, traceout.080312.trc):
-Xtrace:exception.output=traceout.%t.trc,maximal