Diagnosis Guide

Trace information

ATTENTION - READ THIS FIRST
Do not activate this trace facility until you have read this section completely, and understand this 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 performance of your system. 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.

ATTENTION - READ THIS FIRST

Do not activate this trace facility until you have read this section completely, and understand this 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 performance of your system. 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.

Trace facility built into Event Management

The tracing function can be activated by using the haemctrl command. It supplies additional problem determination information when it is requested by the IBM Support Center. Normally, tracing should not be turned on, because it may degrade Event Management subsystem performance and can consume large amounts of disk space in the /var file system.

The trace files are located in the /var/ha/log directory. The following is a brief description of each file:

em.trace.syspar contains trace output from the Event Management daemon.
em.msgtrace.syspar contains message trace output from the Event Management daemon.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]