NonStop SOAP User's Manual

NonStop SOAP Features and Functions
NonStop SOAP User’s Manual—520501-012
4-70
Trace File
Log Messages
The log contains several types of error messages, including:
•
Errors parsing the SDL input file, as described in SOAP Admin Tool Error
Messages on page 5-13. For most of these errors, the corrective action is to
correct the SDL input file and restart the server.
•
SOAP faults, as described in SOAP Faults on page 4-64.
•
Initialization messages, described here.
Trace File
You can use an environment variable called SOAP_TRACE_LEVEL to specify
whether, and at what level, to trace the operation of a SOAP server process. The
environment variable called SOAP_TRACE_FILE specifies the trace file name.
If a SOAP server process is running as a named process or a server class, the trace
output for each server is written to a different file. Each trace file will have a name of
the form:
<name>.<nnn>.<nn>
where name is the value of SOAP_TRACE_FILE.
nnn is the process name of the server.
nn is the log-rotation-value set for the trace file. For more information on setting the
value, see log-rotation-value on page 6-62.
If the trace file already exists when a server process starts up, the server process
appends new trace records to the end of the file.
The server reports these messages to EMS if the trace file cannot be created or
opened:
Error while opening the trace file: name
Error getting the Trace File name suffix: error
where name is the value of SOAP_TRACE_FILE and error is a file-system error
number. The trace file name suffix is the process name appended to the value of
SOAP_TRACE_FILE when the SOAP server runs as a named process or a server
class.
Mapping Between Faults, Error Logs, and Trace Records
Because it identifies the process that reported an error, the error log provides a means
of correlating a fault reported to the client with the detailed information provided in the
trace file. To find the trace file, and the records within a trace file, that explain a specific
error: