For XMS .NET applications, you can configure trace from an application configuration file as well as from the XMS environment variables. You can select the components that you want to trace. Trace is normally used under the guidance of IBM Support.
Tracing for XMS .NET is based on the standard .NET trace infrastructure.
All tracing except for error tracing is disabled by default. You can turn tracing on and configure the trace settings in either of the following ways:
The active trace file has a name of the format xms_trace<PID>.log where <PID> represents the process ID of the application. The size of the active trace file is by default limited to 20 MB. When this limit is reached, the file is renamed and archived. Archived files have names of the format xms_trace<PID>_YY.MM.DD_HH.MM.SS.log
By default, the number of trace files that are retained is four, that is, one active file and three archived files. These four files are used as a rolling buffer until the application stops, with the oldest file being removed and replaced by the newest file. You can change the number of trace files by specifying a different number in the application configuration file, but there must be at least two files (one active file and one archived file).
Two trace file formats are available:
Trace entries contain the following information:
The following example shows an extract from some trace:
[09/11/2005 14:33:46:914276] 00000004 IBM.XMS.Comms.IoRequest > Allocate Entry [09/11/2005 14:33:46:914276] 00000004 IBM.XMS.Comms.IoRequest > Initialize Entry [09/11/2005 14:33:46:914276] 00000004 IBM.XMS.Comms.IoRequest < Initialize Exit [09/11/2005 14:33:46:914276] 00000004 IBM.XMS.Comms.IoRequest < Allocate Exit
In the above, format is:
[Date Time:Microsecs] Thread-id Classname Trace-type Methodname Entry or Exit
where Trace-type is: