OpenEdge Data Management: DataServer for Microsoft SQL Server

Connecting the DataServer
6–32
Using the $UNIQUE_DSLOG environment variable
You can use the $UNIQUE_DSLOG environment variable to isolate the log output of a given
server instance and prevent the sharing of log files resources. When the $UNIQUE_DSLOG
variable is set, the designated DataServer log file name becomes a root name. Specifically, it
becomes the prefix of a log file name that is followed by the process id of the running
server process – which is then suffixed with the familiar .lg extension if the server name is
dataserv. This feature can be disabled by unsetting the UNIQUELOG environment variable.
With a unique name, the server executable can manage its own log file copy. However, the
DSLOG-MANAGER system handle continues to disallow changes to the log file name or closing of
the file at run-time. This restriction ensures that the DataServer always has an open log file to
which it can write information. The legacy qt_debug logging mechanism relies on this being
the case.
For information on managing log settings, see the “Analyzing performance with the Enhanced
Logger” section on page 6–18.
To obtain access to the DataServer log file using the host machine:
1. Before starting up the broker process, set the DSLOGDIR environment variable to the name
of the directory where you want to place the log file.
If you set the environment variable, OpenEdge writes the information to the dataserv.lg
file. If OpenEdge cannot open this file or %DSLOGDIR% is unset, it writes the information to
the dataserv.lg file in the process’ current directory, and appends to it with each
subsequent process that uses it.
2. Open the dataserv.lg file to read the DataServer log.