Trace and core file information
Do not activate this trace facility until you have read this section completely and understand the material. If you are not certain how to properly use this facility, or if you are not under the guidance of IBM® Service, do not activate this facility.
Activating this facility may result in degraded system performance. Activating this facility may also result in longer response times, higher processor loads, and the consumption of system disk resources. Activating this facility may also obscure or modify the symptoms of timing-related problems.
The RMC subsystem uses the common trace facility for tracking the internal activity of the daemon. You may select multiple levels of detail when diagnosing problems. You can activate additional tracing by issuing the /opt/rsct/bin/rmctrace command. RSCT writes the trace data to the /var/ct/IW/log/mc/trace file. You can view contents of the trace file with the rpttr command.
RSCT will write any core file that results from a program error in the RMC subsystem to the /var/ct/IW/run/mc directory. Upon restart, the RMC subsystem renames any core file to core.last. It also removes any prior core file named core.last . If it renames a core file to core.last, then it renames the trace file to trace.last and creates a new trace file. Thus, a trace file named trace.last contains a trace of the daemon activity at the time the core.last file is created.